Master Data Distribution for Customer Data - SAP · Configuration Guide SAP Business One 9.0...

Configuration Guide

SAP Business One 9.0 integration for SAP NetWeaver Document Version: 1.0 – 2013-03-22

PUBLIC

Master Data Distribution for Customer Data All Countries

2

PUBLIC

© 2017 SAP SE or an SAP affiliate company. All

rights reserved.

Master Data Distribution for Customer Data

Typographic Conventions

Typographic Conventions

Type Style Description

Example Words or characters quoted from the screen. These include field names, screen titles,

pushbuttons labels, menu names, menu paths, and menu options.

Textual cross-references to other documents.

Example Emphasized words or expressions.

EXAMPLE Technical names of system objects. These include report names, program names,

transaction codes, table names, and key concepts of a programming language when they

are surrounded by body text, for example, SELECT and INCLUDE.

Example Output on the screen. This includes file and directory names and their paths, messages,

names of variables and parameters, source text, and names of installation, upgrade and

database tools.

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

they appear in the documentation.

<Example> Variable user entry. Angle brackets indicate that you replace these words and characters

with appropriate entries to make entries in the system.

EXAMPLE Keys on the keyboard, for example, F2 or ENTER .


Document History

PUBLIC


rights reserved. 3

Document History

Version Date Change

1.0 2013-03-22 Release to Customer

4

PUBLIC


rights reserved.


Table of Contents

Table of Contents

1 Introduction .............................................................................................................................. 5 1.1 Scenario Description ............................................................................................................................. 5 1.2 Systems and Releases .......................................................................................................................... 6 1.3 Prerequisites .......................................................................................................................................... 7

2 Configuration in SAP ERP........................................................................................................8 2.1 Setting Up Cross-Company Codes ...................................................................................................... 8 2.2 Maintaining the Default Flag in Customer Master Records ............................................................... 9 2.3 Maintaining the Distribution Model ...................................................................................................... 9 2.4 Generating Partner Profiles ................................................................................................................ 10

2.4.1 Changing Partner Profiles ................................................................................................... 11 2.5 Activating Change Pointers ................................................................................................................. 12

2.5.1 Activating Change Pointers for Message Types................................................................ 12 2.6 Defining Variants .................................................................................................................................. 13 2.7 Scheduling Jobs ....................................................................................................................................14

3 Configuration in SAP Business One integration for SAP NetWeaver ................................. 16 3.1 Setting System Type-Specific Properties for the Subsidiary SAP Business One Systems ..........16 3.2 Setting Up and Activating the Scenario Package ..............................................................................19

4 Value Mappings ......................................................................................................................22


Introduction

PUBLIC


rights reserved. 5

1 Introduction

1.1 Scenario Description

Master Data Distribution (MDD) – Customer (sap.MD.BizPartner) distributes centrally maintained master data to

your integrated company network. The scenario package is the foundation for all other integration scenarios.

Master Data Distribution Overview

The scenario consists of the following steps:

Initial setup of your subsidiary SAP Business One with customer master data from the headquarters SAP

ERP.

Keeping the previously distributed customer master data synchronized.

This includes inserts and updates for customer master data records coming from SAP ERP, which is the

central master data server for the integrated company network.

It also implies that the scenario overwrites changes that you maintain in one of the subsidiary systems.

6

PUBLIC


rights reserved.


Introduction

Scenario Steps of Master Data Distribution

The illustration above describes the scenario:

1. In SAP ERP, the customer master data administrator initiates the download of customer records to

connected SAP Business One systems in the subsidiaries or branches.

2. SAP Business One integration for SAP NetWeaver determines the target systems for customer master data.

3. SAP Business One integration for SAP NetWeaver prepares the data for SAP Business One systems. It

provides the expected field structures and values. With an additional call to SAP ERP, SAP Business One

integration for SAP NetWeaver enriches data records with ship-to and bill-to addresses.

4. SAP Business One integration for SAP NetWeaver sends the data to all previously determined SAP Business

One target systems.

5. If there is an update or new record available in SAP ERP, SAP ERP automatically sends the new or updated

information to SAP Business One integration for SAP NetWeaver.

6. SAP Business One integration for SAP NetWeaver sends new and updated information to the relevant SAP

Business One systems.

SAP ERP does not forward deletions.

1.2 Systems and Releases

You can use the scenario with the following systems and releases:

System Release

SAP ERP 4.6C, 4.7.100, 4.7.200, ECC 6.0

SAP Business One SAP Business One 8.8, 8.81, 8.82, 9.0, 9.1, 9.2

SAP Business One 8.82, 9.0, 9.1, 9.2 version for SAP

HANA

SAP Business One integration for SAP NetWeaver 9.0


Introduction

PUBLIC


rights reserved. 7

1.3 Prerequisites

You have installed SAP Business One integration for SAP NetWeaver.

You have set up your technical system landscape connecting to SAP Business One systems and SAP ERP.

You have tested the technical connections.

If you cannot use the scenario packages without changes, copy the scenario steps of the package to your

namespace and adjust the definitions.

For more information about installing SAP Business One integration for SAP NetWeaver and setting up your

technical system landscape, see the Administrator's Guide.

8

PUBLIC


rights reserved.


Configuration in SAP ERP

2 Configuration in SAP ERP

Configuration in SAP ERP that enables the integration process flow consists of the following steps:

Setting up cross-company codes

Maintaining the default flag in customer master records

Maintaining the distribution model

Generating and changing partner profiles

Setting up and enabling change pointers for the message flow trigger

As of ECC 6.0, the configuration steps to set up your integration process using ALE are no longer completely

assigned to the ALE section in IMG. The following procedures describe whether you access functions from the

SAP menu or from IMG.

The SALE transaction SALE contains all necessary ALE customizing IMG steps. You can use this transaction to

make the ALE configuration process easier. This area menu displays only the ALE-relevant customizing entries.

To open IMG, call the SPRO transaction and choose SAP Reference IMG.

2.1 Setting Up Cross-Company Codes

Cross-system company codes are necessary for the distribution of financial accounting data for your product

master records. To set up cross-system company codes, create them in your headquarters SAP ERP and assign

them to the local company codes. Specify identifiers of the relevant cross-system company codes for each of the

individual company codes.

When you send an IDoc with company code-dependent data, the system replaces the company code with the

cross-system company code in all company code fields.

To set up cross-system company codes, create them in your headquarters ERP system and assign them to the

local company codes. Specify the identifiers of the relevant cross-system company codes for each of the

individual company codes.



PUBLIC


rights reserved. 9

2.2 Maintaining the Default Flag in Customer Master Records

In SAP ERP you can maintain more than one partner per customer using the Bill-to Party (BP) partner role.

From a customer‘s partner function, select a partner as the designated Bill to Party default address for the SAP

Business One business partner.

Procedure

To maintain the default flag and to transfer the preferred partner to SAP Business One, change the customer

master as follows:

1. To select your customer master data, in SAP ERP call the XD03 transaction.

2. Choose Sales Area Data and select the Partner Functions tab.

3. Check whether the partner function for BP Bill-to Party has been defined more than once.

4. Select the default flag for the business partner number you want to transfer as the Bill-To default address to

your SAP Business One subsidiary.

Note

The configuration steps above are for SAP ERP, release ECC 6.0. The steps may vary with different

SAP ERP releases. If your system release is not ECC 6.0, see the relevant SAP ERP documentation for

the exact steps.

2.3 Maintaining the Distribution Model

In ALE, you model the message flow that defines the sender and receiver systems, and the message type in the

distribution model.

For master data distribution from SAP ERP to SAP Business One integration for SAP NetWeaver, define the

following for the distribution model:

DEBMAS message type as outbound message

SAP ERP as your sending system

SAP Business One integration for SAP NetWeaver as your receiving system

Prerequisites

You have set up the logical systems for your sender and receiver systems.

You have set up the RFC connection to SAP Business One integration for SAP NetWeaver.

If you have already set up the distribution model for the integration scenario Master Data Distribution –

Product, you do not have to create a new distribution model. You can enhance the existing distribution model

by adding the DEBMAS message type.

For more information about setting up your technical system landscape, see the Administrator's Guide.

10

PUBLIC


rights reserved.



Procedure

1. In SAP ERP, IMG choose SAP NetWeaver Application Server IDoc Interface / Application Link Enabling

(ALE) Modeling and Implementing Business Processes Maintain Distribution Model and Distribute Views.

Alternatively, call the BD64 transaction.

2. Choose Edit and choose Create Model View.

3. In the Create Model View window, specify the following:

o In the Short Text field, enter the name of the distribution model, for example Master Data Distribution to

B1.

The system displays the short text in the distribution model maintenance.

o In the Technical name field enter the technical name of your distribution model, for example MDD_B1.

The technical name of the distribution model is unique.

o In the Start date field, enter the start date of the validity period. The default value is date of creation.

Change the default value only if you want to set the start of validity to a later date.

o In the End date field, enter the last day of the validity period. The default value is 31.12.9999.

Change the default value only if you want to limit the end of validity.

4. To add message types to the distribution model, in the Distribution Model Changed window, select your

previously created distribution model and choose Add message type.

5. In the Add message type window, specify the following:

o In the Model view field, the system displays the name of your distribution model.

o In the Sender field select the logical name of SAP ERP.

o In the Receiver field, select the logical name of SAP Business One integration for SAP NetWeaver.

o In the Message type field, enter DEBMAS.

6. Save your entries.

2.4 Generating Partner Profiles

For each partner with which you exchange business documents, you need a partner profile. In ALE, this partner is

another system, such as SAP Business One integration for SAP NetWeaver. A partner profile specifies parameters

such as the IDoc basis type, to control inbound and outbound message processing with the partner.

Generate the partner profile based on the information already maintained in the distribution model.

Prerequisites

You have defined the distribution model.



PUBLIC


rights reserved. 11

Procedure

1. In SAP ERP, IMG choose SAP NetWeaver Application Server IDoc Interface / Application Link Enabling

(ALE) Modeling and Implementing Business Partner Profiles and Time of Processing Generate Partner

Profiles.


2. In the Generating partner profile window, select the Transfer IDoc immediately radio button.

3. Select the Trigger immediately radio button.

Note

Do not change any of the other default values in this generation window.

4. Choose Execute.

2.4.1 Changing Partner Profiles

If any values are not applicable to the scenario, manually change the values.

Prerequisites

You have generated the partner profile for the distribution model.

Procedure

1. In SAP ERP IMG, choose Tools ALE ALE Administration Runtime Settings Partner Profiles.

Alternatively, call the WE20 transaction.

2. Expand the Partner type LS (Logical system) sub tree.

3. Select the entry for the logical system of the SAP Business One integration for SAP NetWeaver server.

4. In the Outbound parmt. section, select the Message Type DEBMAS column.

5. To display details, choose DetailScreenOutb. Parameter.

6. In the Partner Profiles: Outbound parameters window, select the Outbound Options tab and enter the

following:

Field Name Field Value Description

Transfer IDOC immed. Select the radio button. Outbound parameters:

Output processing immediately

starts for each individual IDoc.

This is the automatic selection

during partner profile generation

If this button is not selected by

default, select it manually.

12

PUBLIC


rights reserved.




Basic type DEBMAS05

Change the default value.

Processing uses DEBMAS05 for

data communication.

The system displays it

automatically when you generate

the partner profile.


2.5 Activating Change Pointers

Activate the change pointers in the system. Change pointers are deactivated in the SAP standard system.

Note

As of SAP ERP release ECC 6.0, you do not have to maintain number ranges for change pointers.

For more information about how to maintain number ranges for change pointers with the BDCP

transaction, see the standard documentation in the reference IMG.

Procedure

1. From the IMG menu, choose SAP NetWeaver Application Server IDoc Interface / Application Link

Enabling (ALE) Modeling and Implementing Business Processes Master Data Distribution Replication of

Modified Data Activate Change Pointers - Generally.


2. In the Activate Change Pointers – Generally window, enter the following:


Change pointers Activated -

Generally

Select the checkbox. In ALE, these are active indicators

for various tools.


2.5.1 Activating Change Pointers for Message Types

Activate the writing of change pointers for each message type, for example, DEBMAS (customer master data).

Procedure



Modified Data Activate Change Pointers for Message Types.



PUBLIC


rights reserved. 13

2. In the Change View “Activate Change pointer for message type”: Overview window, check if the DEBMAS

message type is available.

o If it is available, select the checkbox for the message type.

o If it is not available, choose New Entries. and in the New Entries: Overview window, enter the following:

Field name Field Value Description

Message Type DEBMAS Message type for master data

distribution

Activate Select checkbox ALE active indicators for the

DEBMAS message type


2.6 Defining Variants

To distribute master data changes, schedule a report that reads the change pointers and generates IDocs. Define

variants for the report and schedule jobs, each with the report and a variant, as one step.

You define variants for the RBDMIDOC program. You can use system-defined variants for the standard message

types.

Procedure



Modified Data Create IDocs from Change Pointers Define Variants.

Alternatively, call the RBDMIDOC transaction.

2. Select New Entries, and in the ABAP Editor: Initial window, enter the following:


Program RBDMIDOC This is the program to distribute

changes for product master data.

Variants Select radio button

3. Choose Change, and in the ABAP Variants: Initial Screen window, enter the following:


Variant <Name of variant>

Example: CUSTOMER

4. Choose Create, and in the Maintain Variant: Report RBDMIDOC, Variant <name of variant> window, enter the

following:


Message Type DEBMAS

14

PUBLIC


rights reserved.



5. Choose Attributes, and in the Variant Attributes window, enter the following:


Meaning Enter a description for your

variant.

Example: Variant for MDD –

Customer


2.7 Scheduling Jobs

This section describes how to schedule jobs for the periodic creation of intermediate documents (IDocs) for

master data. You schedule the jobs for each defined variant, hence, for each message type. If you want to

distribute customer master, plan a job for the DEBMAS message type that periodically checks changes and

generates IDocs.

Procedure



Modified Data Create IDocs from Change Pointers Define Variants.

Alternatively, call the RBDMIDOC transaction.

2. In the ABAP Editor: Initial Screen window, enter the following:


Program RBDMIDOC This is the program to distribute

changes for customer master

data.

3. To define a job, choose System Services Jobs Define Jobs.

4. In the Define Background Job window, enter the following:


Job name <Job name>

Example: MDD_CUSTOMER

Job class <Job class>

Select the priority according to

your requirements.

This is a classification of

background jobs according to

priority and job type.

Exec. Target <host name>_<SAP System

name>_<SAP System number>

Name of an SAP instance where

the system executes the

background job.

Host name is the name of the

server computer on which the



PUBLIC


rights reserved. 15


instance runs. The system profile

parameter SAPLOCALHOST

contains this information.

The name of each instance is

specified in the system profile

parameter rdisp/myname.

5. Choose Start Condition, and in the Start Time window, select the following:

o The required starting time, for example, Immediate.

o The Periodic job checkbox

o The required Period values option, for example, Hourly.


7. Choose Step, and in the Create Step 0 window, enter the following:


Variant <Variant name>

For example: MDD_CUSTOMER

This is the name of the previously

created variant for sending IDocs

for the DEBMAS message type.

8. Save your entries and save the job.

16

PUBLIC


rights reserved.


Configuration in SAP Business One integration for SAP NetWeaver

3 Configuration in SAP Business One integration for SAP NetWeaver

3.1 Setting System Type-Specific Properties for the Subsidiary SAP Business One Systems

Maintain SysID-specific properties for each subsidiary in the system landscape. System ID-specific properties are

available per system type. When you create a system landscape entry, this entry gets a unique system ID (SysID).

You can maintain fixed values for properties for the SysID.

SAP Business One integration for SAP NetWeaver accesses the properties at runtime and uses them for message

processing, for example for automatically setting defaults, option selection, and so on.

All scenario packages that use the systems as senders or receivers, can access the SysID-specific properties.

From a business point of view, the aim of using the SysID-specific properties is to place the subsidiary in the

company organization environment. In the large account environment, the settings represent the organizational

entity of the subsidiary from the headquarters’ point of view. The settings describe the subsidiary with SAP ERP

organization units. For example, the subsidiary represents the sales channel for the headquarters’ products in a

foreign country.

Prerequisites

You have set up the system landscape with all sender and receiver systems in SAP ERP and in SAP Business One

integration for SAP NetWeaver.

For more information about setting up your technical system landscape, see the Administrator's Guide.

Procedure

1. To start SAP Business One integration for SAP NetWeaver, choose Start All Programs SAP Business One

integration for SAP NetWeaver SAP Business One integration for SAP NetWeaver.

2. To log on, in the B1i Administrative Login user interface, enter the user name and password.

3. Choose SLD and select the SLD entry for your subsidiary.

4. Select the Properties button to set the following properties:


Company Code <Company code key from ERP

system>

This is a four-digit key

representing the company code.

For company code values or

entries, see the company codes in

the headquarters SAP ERP

system.

When you enter the company

code representing your



PUBLIC


rights reserved. 17


It structures the business

organization from a financial

accounting perspective.

subsidiary in your network,

financial accounting-specific data

is selected from the SAP ERP

message accordingly.

Company Language Language key>

Example: EN English

It defines the main company

language for the subsidiary and

enables access to the language-

dependent values in the message,

valid for the respective target

subsidiary system.

For country-specific values or

entries, see the ISO codes for

countries.

Country <Country key> Example: EN ISO

code for UK

Enables access to the country-



subsidiary system

For country-specific values or


countries.

Credit Control Area <Credit Control Area key from

ERP system>

The four-digit key represents the

credit control area.

Used as an organizational unit

that specifies and checks the

credit limit for customers

For credit control area values or

entries, see the credit control

area set up in your headquarters

SAP ERP system.

When you enter the credit control

area representing your subsidiary

in the company network,

processing selects credit control

area-specific data from the SAP

ERP message.

Distribution Channel <Distribution channel key from

ERP system>

The two-digit key represents the

distribution channel.

Used to structure the business

organization from a distribution

channel perspective. You can set

up distribution channel-specific

data per customer master data

record, to maintain, for example,

specific conditions and pricing.

For distribution channel values or

entries, see the distribution

channels set up in the

headquarters SAP ERP

Refer to the organizational

structure set up in the

headquarters SAP ERP

When you enter the distribution

channel representing your

subsidiary in the company

network, processing selects

distribution channel-specific data

from the SAP ERP message.

A distribution channel is not a

single filter or selection criterion.

18

PUBLIC


rights reserved.




It is used in combination with a

sales organization and (for some

master data) with a division.

The combination of the keys

represents the SAP ERP sales

area.

Division <Division key from ERP system>

The two-digit key represents the

product division.


organization from a product

division perspective. You can set

up product division-specific data

per customer master data

record, to maintain, for example,

specific conditions and pricing.

For the product division values or

entries, see the product divisions

set up in your headquarters SAP

ERP system.

When you enter the division

representing your subsidiary in

the company network, processing

selects division-specific data

from the SAP ERP message.

A division is not a single filter or

selection criterion. It is used in

combination with a sales

organization and a distribution

channel.

The combination of the keys

represents the SAP ERP sales

area.

Foreign Language <Language key>

Example: DE German

It defines the foreign company

language for the subsidiary and

enables access to the language-



subsidiary system.

For language-specific values or


countries.

Sales Organization <Sales organization key from

ERP system>

The four-digit key represents the

sales organization.


organization from a sales

perspective.

You can set up sales-specific data

per customer master data record,

to maintain, for example, specific

conditions and pricing.

For sales organization values or

entries, see the sales

organizations set up in your

headquarters SAP ERP system.

When you enter the sales

organization representing your

subsidiary in the company

network, processing selects sales



PUBLIC


rights reserved. 19


organization-specific data from

the SAP ERP message.

A sales organization is the highest

summation level (after the Client

organizational unit) for sales

statistics with their own statistics

currency.

Note

All other properties are not relevant for the current scenario. You can ignore them.

5. Save your settings.

3.2 Setting Up and Activating the Scenario Package

You use the setup functions of scenarios to configure your master data distribution customer scenario.

To set up the scenario, do the following:

Select the scenario steps.

Select the sender system.

Select the receiver systems.

Set up filter definitions (optional).

Setup a global property.

Define value mappings.

You can use either the existing integration framework functions or the setup wizard ( ). The description below

uses the setup wizard.

Procedure

1. To start SAP Business One integration for SAP NetWeaver, choose Start All Programs SAP Business One

integration for SAP NetWeaver SAP Business One integration for SAP NetWeaver.

2. To log on, in the B1i Administrative Login user interface, enter the user name and password.

3. To setup your scenario, choose Scenarios Setup.

4. In the Scenario Package Identifier field, select the sap.MD.BizPartner scenario package and choose

(Setup Wizard).

The Selection of Scenario Steps step displays the scenario step.

5. Select the Activate checkbox for the sap.R3CUST2B1BP scenario step, and then the Save button and Next.

In the Senders and Receivers step, the integration framework displays all potential sender and receiver

systems for the scenario package.

6. In the Senders section select your headquarters system. In the Receivers section, select all subsidiary SAP

Business One systems and choose Next.

The headquarters system is the sender and all subsidiary systems are the receivers in this scenario.

20

PUBLIC


rights reserved.



7. In the Filter Definition step, the integration framework displays all activated scenario steps for all selected

sender and receiver systems.

o In the Sender Filters section, define filter criteria that are the same for all receiver systems.

o In the SenderReceivers Filters section, define filter criteria that are different for receiver systems.

o By default, all combinations are selected with the checkbox in front of each row. Do not deselect any

combination, even if you do not define any filters for the combination. If you deselect any

combination, the integration framework filters everything.

Set the following filters, choose Save and Next:


Country <Country key in SAP ERP> This is the key in SAP ERP that

determines country-specific

settings for a customer, such as

the length of the postal code or

the bank account number.

Values in the LAND1 field of SAP

ERP T005 system table are valid

filter criteria entries.

The values are usually two-digit

ISO codes that SAP provides as a

default.

Region <Region key in SAP ERP> Depending on the country, the

region may or may not be part of

the address.

Values in the BLAND field of SAP

ERP T005S system table are valid

filter criteria entries.

Regional Market <Value for regional market in

SAP ERP>

This is an SAP ERP system

master data field; you are free to

define any values. There is no

check table available.

8. In the Global Properties step, enter a value for the TextID global property, save your settings and choose Next.


TextID <Key for headquarters text ID> This is a four-digit key for the SAP

ERP system text. It is available in

general data.

The system transfers the SAP

ERP business partner:

customer texts general data

segments to the SAP Business

One Business Partner:

Customer field.

Create the text ID for the KNA1

text object.



PUBLIC


rights reserved. 21

9. You do not need to define local properties, choose Next until you reach the Value Mapping step.

10. In the Value Mapping user interface, define values for available mappings and for all system combinations;

choose Next. Optional mappings are marked as such.

To create a value mapping, choose New.

o In the Mapping Definitions section, to select the sender system, choose the … (ellipsis) button.

o To select a receiver system, choose the second the … (ellipsis) button.

o To define mapping values, choose the Modify button.

In the Value Mapping Table that opens, do the following.

o To add a value pair, click the Add button.

o In the first field, enter the sender system value.

o In the second field, enter the receiver system value.

o Save your settings and close the window.

The following value mappings are available:

o CollectionAuthoriation

o CreditCardCode

o DefaultAccount (optional)

Use it to map the bank account number.

o DefaultBankCode (optional)

Use it to map the bank code.

o DefaultBranch (optional)

Use it to map the name of the bank branch.

o DunningTerm

o GroupCode

o PaymentBlockDescription

o PaymentMethodCode

o PaymentTermsGrpCode

o Priority

o SalesPersonCode (optional)

o ShippingType

o State

o Territory

For more information about how to use the value mapping function, see the Operations Guide, section 1.1.6.2

Setting up Value Mappings

11. As there are no scheduler settings necessary, choose Next, and finally choose Deploy to finalize the scenario

setup.

12. To activate your scenario, choose the Activate button.

22

PUBLIC


rights reserved.


Value Mappings

4 Value Mappings

If the default values in the table below do not already exist in SAP ERP and SAP Business One, enter them

manually.

SAP ERP

Customizing Table Values

SAP Business One

integration for SAP

NetWeaver

Value Mapping Table

SAP Business One

Value Table Default Values

T151

Customers:

Customer Groups

01 Industry

02 Retail

GroupCode OCRG

Customer Groups

(Type C)

100 Customers

101 Vendors

T047A

Account Level

Dunning Control

0001 Four-level

dunning notice, every

two weeks

0003 Payment

reminder, every two

weeks

0005 Four-level

dunning notice, every

two weeks, RE forms

DunningTerm ODUT

Dunning Levels

No default

values available

TVCIN

Payment cards: Type

AMEX

MC

VISA

and so on

CreditCardTypes OCRC

Credit Cards

No default

values available

T008

Payment blocks

' Free for payment

* Skip account

A Blocked for

payment

B Blocked for

payment

N Postprocess

inc.pmnt

P Payment request

R Invoice verification

V Payment clearing

PaymentBlockDescri

ption

OPYB

Payment Blocks

1 Inability to

pay

2 Poor quality

3 Disputed

items

4 Legal action

KNA1

Customer number

No default values

available

SalesPersonCode OSLP

Sales Employees

If not provided,

the system sets

name of KUN2.


Value Mappings

PUBLIC


rights reserved. 23

SAP ERP


SAP Business One

integration for SAP

NetWeaver

Value Mapping Table

SAP Business One


T042E

Company Code-

Specific

Specifications for

Payment Methods

A Bank direct debit

E Automatic debit

F Debit for one-time

customer (CPD)

K Bank check for

foreign payment

L Foreign bank

transfer

O Order check

P Postal check

transfer

R European transfer

S Check

T Check/Bill of

exchange

U Bank transfer

V Clearing (in a

group)

W Bill of exchange

(foreign payment)

CollectionAuthori-

zation

There is no value

table available, but

fixed values for yes

and no.

tYES

tNO

TVSB

Shipping Conditions

01 As soon as

possible

02 Standard

03 Collect

processing

04 Transport Service

05 Just-in-time

06 Synch to

production

08 TVPS Multimode

09 Pick up

10 Immediately

20 Domestic 24/48h

ShippingType OSHP

Shipping Types

No default

values available

T042Z

Payment Methods

for Automatic

Payment

(Dependent on

Country Key. More

than one payment

method may be

selected)

PaymentMethodCode OPYM

Payment Methods

No default

values available

24

PUBLIC


rights reserved.


Value Mappings

SAP ERP


SAP Business One

integration for SAP

NetWeaver

Value Mapping Table

SAP Business One


A ACH

U International Bank

Transfer

C Check

S Single Check

T Bank Transfer

W Fed Wire

T171

Customers: Sales

Districts

000001 Northern

Region

…

US0015 US Midwest

Region

…

Territory OTER

Territory

No default

values available

T052

Terms of Payment

0001 Payable

immediately Due net

0002 Within 14 days

3% cash discount

…

NT30 Net 30

…

PayTermsGrpCode OCTG

Payment Terms

-1 Monetary

basis

3 Discount

T005U

Region (State,

Province, County)

01 Schleswig-

Holstein

02 Hamburg

03 Lower Saxony

04 Bremen

05 Nrth Rhine

Westfalia

06 Hessen

07 Rhineland

Palatinate

08 Baden-

Wurttemberg

09 Bavaria

10 Saarland

11 Berlin

12 Brandenburg

13 Mecklenburg-

Vorpomm.

State OCST

Code


Value Mappings

PUBLIC


rights reserved. 25

SAP ERP


SAP Business One

integration for SAP

NetWeaver

Value Mapping Table

SAP Business One


14 Saxony

15 Saxony-Anhalt

16 Thuringia

TPRIT

Customers: Delivery

Priorities

Priority OBPP

Business Partner

Priorities

www.sap.com/contactsap

© 2017 SAP SE or an SAP affiliate company. All rights reserved.

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

The information contained herein may be changed without prior

notice.

Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software

vendors. National product specifications may vary.

These materials are provided by SAP SE 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 and other SAP products and services mentioned herein as well

as their respective logos are trademarks or registered trademarks of

SAP AG in Germany and other countries.

Please see http://www.sap.com/corporate-

en/legal/copyright/index.epx#trademark for additional trademark

information and notices.

Master Data Distribution for Customer Data - SAP · Configuration Guide SAP Business One 9.0...

Documents

Transcript of Master Data Distribution for Customer Data - SAP · Configuration Guide SAP Business One 9.0...