WIXLIB

Procedure1.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 PartnerProfiles.Alternatively, call the BD82 transaction.2.In the Generating partner profile window, select the Transfer IDoc immediately radio button.3.Select the Trigger immediately radio button.NoteDo not change any of the other default values in this generation window.4. Choose Execute.2.4.1Changing Partner ProfilesIf any values are not applicable to the scenario, manually change the values.PrerequisitesYou have generated the partner profile for the distribution model.Procedure1.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 thefollowing:Field NameField ValueDescriptionTransfer IDOC immed.Select the radio button.Outbound parameters:Output processing immediatelystarts for each individual IDoc.This is the automatic selectionduring partner profile generationIf this button is not selected bydefault, select it manually.PUBLICMaster Data Distribution for Customer DataConfiguration in SAP ERP 2017 SAP SE or an SAP affiliate company. Allrights reserved.11

Field NameField ValueDescriptionBasic typeDEBMAS05Processing uses DEBMAS05 fordata communication.Change the default value.The system displays itautomatically when you generatethe partner profile.7.Save your entries.2.5Activating Change PointersActivate the change pointers in the system. Change pointers are deactivated in the SAP standard system.NoteAs 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 BDCPtransaction, see the standard documentation in the reference IMG.Procedure1.From the IMG menu, choose SAP NetWeaver Application Server IDoc Interface / Application LinkEnabling (ALE) Modeling and Implementing Business Processes Master Data Distribution Replication ofModified Data Activate Change Pointers - Generally.Alternatively, call the BD61 transaction.2.3.In the Activate Change Pointers – Generally window, enter the following:Field NameField ValueDescriptionChange pointers Activated GenerallySelect the checkbox.In ALE, these are active indicatorsfor various tools.Save your entries.2.5.1Activating Change Pointers for Message TypesActivate the writing of change pointers for each message type, for example, DEBMAS (customer master data).Procedure1.From the IMG menu, choose SAP NetWeaver Application Server IDoc Interface / Application LinkEnabling (ALE) Modeling and Implementing Business Processes Master Data Distribution Replication ofModified Data Activate Change Pointers for Message Types.PUBLIC12 2017 SAP SE or an SAP affiliate company. Allrights reserved.Master Data Distribution for Customer DataConfiguration in SAP ERP

2.In the Change View “Activate Change pointer for message type”: Overview window, check if the DEBMASmessage 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:3.Field nameField ValueDescriptionMessage TypeDEBMASMessage type for master datadistributionActivateSelect checkboxALE active indicators for theDEBMAS message typeSave your entries.2.6Defining VariantsTo distribute master data changes, schedule a report that reads the change pointers and generates IDocs. Definevariants 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 messagetypes.Procedure1.From the IMG menu, choose SAP NetWeaver Application Server IDoc Interface / Application LinkEnabling (ALE) Modeling and Implementing Business Processes Master Data Distribution Replication ofModified Data Create IDocs from Change Pointers Define Variants.Alternatively, call the RBDMIDOC transaction.2.3.Select New Entries, and in the ABAP Editor: Initial window, enter the following:Field NameField ValueDescriptionProgramRBDMIDOCThis is the program to distributechanges for product master data.VariantsSelect radio buttonChoose Change, and in the ABAP Variants: Initial Screen window, enter the following:Field NameField ValueVariant Name of variant DescriptionExample: CUSTOMER4. Choose Create, and in the Maintain Variant: Report RBDMIDOC, Variant name of variant window, enter thefollowing:Field NameField ValueMessage TypeDEBMASDescriptionPUBLICMaster Data Distribution for Customer DataConfiguration in SAP ERP 2017 SAP SE or an SAP affiliate company. Allrights reserved.13

5.Choose Attributes, and in the Variant Attributes window, enter the following:Field NameField ValueMeaningEnter a description for yourvariant.DescriptionExample: Variant for MDD –Customer6. Save your entries.2.7Scheduling JobsThis section describes how to schedule jobs for the periodic creation of intermediate documents (IDocs) formaster data. You schedule the jobs for each defined variant, hence, for each message type. If you want todistribute customer master, plan a job for the DEBMAS message type that periodically checks changes andgenerates IDocs.Procedure1.From the IMG menu, choose SAP NetWeaver Application Server IDoc Interface / Application LinkEnabling (ALE) Modeling and Implementing Business Processes Master Data Distribution Replication ofModified Data Create IDocs from Change Pointers Define Variants.Alternatively, call the RBDMIDOC transaction.2.3.In the ABAP Editor: Initial Screen window, enter the following:Field NameField ValueDescriptionProgramRBDMIDOCThis is the program to distributechanges for customer masterdata.To define a job, choose System Services Jobs Define Jobs.4. In the Define Background Job window, enter the following:Field NameField ValueJob name Job name DescriptionExample: MDD CUSTOMERJob class Job class Select the priority according toyour requirements.Exec. Target host name SAP Systemname SAP System number This is a classification ofbackground jobs according topriority and job type.Name of an SAP instance wherethe system executes thebackground job.Host name is the name of theserver computer on which thePUBLIC14 2017 SAP SE or an SAP affiliate company. Allrights reserved.Master Data Distribution for Customer DataConfiguration in SAP ERP

Field NameField ValueDescriptioninstance runs. The system profileparameter SAPLOCALHOSTcontains this information.The name of each instance isspecified in the system profileparameter 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 checkboxo The required Period values option, for example, Hourly.6. Save your entries.7.Choose Step, and in the Create Step 0 window, enter the following:Field NameField ValueDescriptionVariant Variant name This is the name of the previouslycreated variant for sending IDocsfor the DEBMAS message type.For example: MDD CUSTOMER8. Save your entries and save the job.PUBLICMaster Data Distribution for Customer DataConfiguration in SAP ERP 2017 SAP SE or an SAP affiliate company. Allrights reserved.15

3Configuration in SAP Business Oneintegration for SAP NetWeaver3.1Setting System Type-Specific Properties for the SubsidiarySAP Business One SystemsMaintain SysID-specific properties for each subsidiary in the system landscape. System ID-specific properties areavailable 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 messageprocessing, 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 thecompany organization environment. In the large account environment, the settings represent the organizationalentity of the subsidiary from the headquarters’ point of view. The settings describe the subsidiary with SAP ERPorganization units. For example, the subsidiary represents the sales channel for the headquarters’ products in aforeign country.PrerequisitesYou have set up the system landscape with all sender and receiver systems in SAP ERP and in SAP Business Oneintegration for SAP NetWeaver.For more information about setting up your technical system landscape, see the Administrator's Guide.Procedure1.To start SAP Business One integration for SAP NetWeaver, choose Start All Programs SAP Business Oneintegration 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:Field NameCompany CodeField ValueDescription Company code key from ERPsystem This is a four-digit keyrepresenting the company code.For company code values orentries, see the company codes inthe headquarters SAP ERPsystem.When you enter the companycode representing yourPUBLIC16 2017 SAP SE or an SAP affiliate company. Allrights reserved.Master Data Distribution for Customer DataConfiguration in SAP Business One integration for SAP NetWeaver

Field NameCompany LanguageField ValueDescriptionIt structures the businessorganization from a financialaccounting perspective.subsidiary in your network,financial accounting-specific datais selected from the SAP ERPmessage accordingly.Language key It defines the main companylanguage for the subsidiary andenables access to the languagedependent values in the message,valid for the respective targetsubsidiary system.Example: EN EnglishFor country-specific values orentries, see the ISO codes forcountries.Country Country key Example: EN ISOcode for UKEnables access to the countrydependent values in the message,valid for the respective targetsubsidiary systemFor country-specific values orentries, see the ISO codes forcountries.Credit Control Area Credit Control Area key fromERP system The four-digit key represents thecredit control area.Distribution ChannelFor credit control area values orentries, see the credit controlarea set up in your headquartersSAP ERP system.Used as an organizational unitthat specifies and checks thecredit limit for customersWhen you enter the credit controlarea representing your subsidiaryin the company network,processing selects credit controlarea-specific data from the SAPERP message. Distribution channel key fromERP system For distribution channel values orentries, see the distributionchannels set up in theheadquarters SAP ERPThe two-digit key represents thedistribution channel.Used to structure the businessorganization from a distributionchannel perspective. You can setup distribution channel-specificdata per customer master datarecord, to maintain, for example,specific conditions and pricing.Refer to the organizationalstructure set up in theheadquarters SAP ERPWhen you enter the distributionchannel representing yoursubsidiary in the companynetwork, processing selectsdistribution channel-specific datafrom the SAP ERP message.A distribution channel is not asingle filter or selection criterion.PUBLICMaster Data Distribution for Customer DataConfiguration in SAP Business One integration for SAP NetWeaver 2017 SAP SE or an SAP affiliate company. Allrights reserved.17

Field NameField ValueDescriptionIt is used in combination with asales organization and (for somemaster data) with a division.The combination of the keysrepresents the SAP ERP salesarea.Division Division key from ERP system The two-digit key represents theproduct division.It structures the businessorganization from a productdivision perspective. You can setup product division-specific dataper customer master datarecord, to maintain, for example,specific conditions and pricing.For the product division values orentries, see the product divisionsset up in your headquarters SAPERP system.When you enter the divisionrepresenting your subsidiary inthe company network, processingselects division-specific datafrom the SAP ERP message.A division is not a single filter orselection criterion. It is used incombination with a salesorganization and a distributionchannel.The combination of the keysrepresents the SAP ERP salesarea.Foreign Language Language key It defines the foreign companylanguage for the subsidiary andenables access to the languagedependent values in the message,valid for the respective targetsubsidiary system.Example: DE GermanFor language-specific values orentries, see the ISO codes forcountries.Sales Organization Sales organization key fromERP system The four-digit key represents thesales organization.It structures the businessorganization from a salesperspective.You can set up sales-specific dataper customer master data record,to maintain, for example, specificconditions and pricing.For sales organization values orentries, see the salesorganizations set up in yourheadquarters SAP ERP system.When you enter the salesorganization representing yoursubsidiary in the companynetwork, processing selects salesPUBLIC18 2017 SAP SE or an SAP affiliate company. Allrights reserved.Master Data Distribution for Customer DataConfiguration in SAP Business One integration for SAP NetWeaver

Field NameField ValueDescriptionorganization-specific data fromthe SAP ERP message.A sales organization is the highestsummation level (after the Clientorganizational unit) for salesstatistics with their own statisticscurrency.NoteAll other properties are not relevant for the current scenario. You can ignore them.5.Save your settings.3.2Setting Up and Activating the Scenario PackageYou 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 (uses the setup wizard.). The description belowProcedure1.To start SAP Business One integration for SAP NetWeaver, choose Start All Programs SAP Business Oneintegration 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 receiversystems for the scenario package.6. In the Senders section select your headquarters system. In the Receivers section, select all subsidiary SAPBusiness One systems and choose Next.The headquarters system is the sender and all subsidiary systems are the receivers in this scenario.PUBLICMaster Data Distribution for Customer DataConfiguration in SAP Business One integration for SAP NetWeaver 2017 SAP SE or an SAP affiliate company. Allrights reserved.19

7.In the Filter Definition step, the integration framework displays all activated scenario steps for all selectedsender 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 anycombination, even if you do not

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. . o In the Short Text field, enter the name of the distribution model, for example Master Data Distribution to B1.