creating line structures with alternatives

8/10/2019 Creating Line Structures With Alternatives

http://slidepdf.com/reader/full/creating-line-structures-with-alternatives 1/24

AP Application Platform

Release Notes

SAP ERP Central Component

Release 6.0



© 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 permissionof 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 softwarevendors.

Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server ® are registered trademarks of Microsoft Corporation.

IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®, AS/400®, OS/390®, and

OS/400® are registered trademarks of IBM Corporation.

ORACLE® is a registered trademark of ORACLE Corporation.

INFORMIX®-OnLine for SAP and Informix® Dynamic Server TM

are registered trademarks of Informix Software

Incorporated.

UNIX®, X/Open®, OSF/1®, and Motif ® are registered trademarks of the Open Group.

Citrix®

, the Citrix logo, ICA®

, Program Neighborhood®

, MetaFrame®

, WinFrame®

, VideoFrame®

, MultiWin®

and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML 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 andimplemented by Netscape.

SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI,

SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com are trademarks or registered trademarks of SAP AGin Germany and in several other countries all over the world. All other products mentioned are trademarks or registered

trademarks of their respective companies.

Design: SAP Communications Media



1 AP Application Platform 11.1 AP-PPE Integrated Product

Engineering 1

1.1.1 Archiving iPPE Objects (New) 1

1.1.2 Authorization Objects in iPPE and Delta Ma

(New) 1

1.1.3 Connection of Project System to the iPPE W

Professional (New) 2

1.1.4 Overview of New Functions in Line Design 3

1.1.5 IPPE-Line Design 4

1.1.6 BAPIs for Replicating iPPE Objects 6

1.1.7 Release Management (New) 7

1.2 AP-MD Master Data 7

1.2.1 AP-MD-IBA Installed Base 7

1.2.1.1 Installed Base Management (Changed) 8

1.2.2 AP-MD-BF Basic Functions 8

1.2.2.1 AP-MD-BF-SYN Master Data Synchronization 8

1.2.2.1.1 Changes to the UI of the SAP Business Part

Services 9

1.2.2.1.2 Customer/Vendor Integration (Enhanced) 12

1.2.2.1.3 Changes to the IMG for the SAP Business Pa

Financial Services 151.2.2.1.4 Synchronization Cockpit (New) 17

1.2.2.1.5 Master Data Synchronization (New) 18

1.3 AP-PRC Pricing & Condition Technique 19

1.3.1 AP-PRC-CON Konditionstechnik 19

1.3.1.1 19

1.3.1.2 19

1.3.1.3 19

1.4 AP-TTE Transaction Tax Engine 19

1.4.1 19

______________________________________________________________

Release-Informationen Inhaltsverzeichnis SAP AG ______________________________________________________________



1 AP Application Platform

1.1 AP-PPE Integrated Product and Process Engineering

1.1.1 Archiving iPPE Objects (New)

Use

As of SAP ECC 6.0 (SAP_APPL 600), you can archive iPPE objects and structures. You can use the

following archiving objects:

- CA_PPEACT

For line routings

- CA_PPECMP

For

- Product structures (product variant structures and assemblies)

- Color schemes and variants

- Engineering nodes and structures

- Focus structures

- CA_PPEFLO

For lines and line networks

You can select iPPE objects and structures for archiving in one of the following ways:

- Via the node name

- Via materials (only valid for CA_PPECMP)

- Via the focus name (only valid for CA_PPECMP)

- Via change numbers (only valid for CA_PPECMP)

Effects on Existing Data

- The system checks if the structures that you want to archive are used in a production version. If this

is the case, the structures cannot be archived. The product version must first be deleted in order for

the structures to be archived.

- Routings, material assignments, and line balances are not archived.

______________________________________________________________

SAP-System ______________________________________________________________



1.1.2 Authorization Objects in iPPE and Delta Maintenance in APIs (New)

Use

As of SAP ECC 6.0, the following changes have been made to authorization objects within iPPE:

- The authorization object C_PVS_PAID (iPPE Alternative: External Key) is obsolete. It has been

replaced by the authorization object C_PPE_PAID (iPPE Alternative: External Key).

- The authorization object C_PPE_ARC is available for archiving iPPE objects. For more

information about archiving, see the Release Note Archiving iPPE Objects (New).

- The function for delta maintenance has been added to the function modules

PVSHI_PNCMP_MAINTAIN and PVSHI_PVCMP_MAINTAIN.

For more information, see the section "Delta Maintenance in Function Modules:

- PVSHI_PNCMP_MAINTAIN (iPPE: Maintain Nodes of Product Structure)

- PVSHI_PVCMP_MAINTAIN (iPPE: Maintain Variants of Product Structure)

Effects on System Administration

Adapt the authorizations for the users. Do not use the authorization object C_PVS_PAID any more. Usethe authorization object C_PPE_PAID instead.

1.1.3 Connection of Project System to the iPPE Workbench Professional (New)

Use

During development and production of complex series products such as automobiles and computers, the

development of the production process is extremely important to how the product is actually developed.You can display the administration and execution of Engineering projects in the early stages of product

development in iPPE. The project system allows you to plan, analyze, control, and monitor dates, costs,

and resources as well as documents and drawings.

In the early phases of product development, the product structure, together with time scheduling, provides

the entire basis for all participants. This is why the objects of the iPPE product structure are considered

when connecting the project system.

- Assign WBS elements, reference points, and network activities to structure nodes and assemblies.

- Assign WBS elements, reference points, and network activities to variants of the product structure.

______________________________________________________________

SAP-System ______________________________________________________________



- Display the elements of the SAP Project System assigned to the iPPE objects in the navigation area

in the iPPE Workbench Professional.

- Assign iPPE objects to elements in the project system via a tab page in the detail area of the iPPE

Workbench Professional.

- Evaluate the assignments between iPPE and PS elements via an interface, and transfer the materials

in the product structure to the project system.

Effects on Customizing

Production -> Master Data -> Integrated Product Engineering -> Business Add-Ins for Integrated Product

and Process Engineering -> BAdI: iPPE Connection to Project System

See also

Release Information: Integration of iPPE with the Project System (New)

1.1.4 Overview of New Functions in Line Design

Use

With iPPE Line Design, you can create the structure and characteristics of takt-based production lines in

the system.

Previously, you could use Line Design to reproduce individual production lines or a linear series of

production lines only. As of Release DI 4.6C2, you can also create complex line networks, consisting of

alternatives lines, in the system. This enables you to describe the alternative paths through a line network,

through which various products can run. The data is available for other applications, such as model mix

planning, material staging, and backflushing. The following new line elements have been introduced to

make this possible:

- Group of alternative lines

- Alternative line

- Part of line-network

You can find more information on reproducing complex line networks under Creating Line Structures

with Alternatives.

You can also use multiple work centers to represent alternative paths through a line network. A multiple

work center represents a group of work centers at which exactly the same work is carried out. You

include a multiple work center in a line structure if you have alternative work centers on a production

line, which receive supplies from different supply areas. An order can be processed at either one of the

work centers. You specify which work center has been used when you backflush. You can find more

information under Creating Multiple Work Centers.

The following new functions and enhancements are also available:

______________________________________________________________

SAP-System ______________________________________________________________



- New line elements to improve structuring within a line structure:

- Line area

- Intermediate buffer

- Introduction of action points

- Connection to control cycle maintenance

There is a tab page for maintaining control cycles when you maintain line elements. For more

information, see Mass Maintenance of Control Cycles.

- Discontinuation of line resources in the DI system

Previously, you had to create a line resource in the DI system and assign it to the line node. As of

this Release, line resources are automatically generated from line nodes when iPPE data is

transferred into the APO. Der APO adopts the name, which you specify in the basic data for theproduction line in the Line Resource , and the plant. You must complete data that is relevant for

planning manually in the APO, such as the production rate, shift sequence, and so on.

Effects on Existing Data

After upgrading, you can no longer display line resources that you have created in the DI System.

However, an XPRA conversion ensures that these resources remain available as line resources in the

APO.


The activity Define Line-Specific Relationship Subtypes has been added to iPPE Customizing in the Line

Design Area. The Customizing entries for these new types have already been made.

1.1.5 IPPE-Line Design

Scope of Functions

This component serves to create the structure and characteristics of your production line as master data in

the system, within integrated product and process engineering.

You can represent both simply structred production lines as well as highly-complex assembly lines, for

automobile production, for example. For complex assembly lines you can also carry out a line balance, in

which you define the optimum work content of the individual line segments.

Implementation guidelines

iPPE Line Design is suitable for takt-based repetitive or flow manufacturing in which the work stations

are linked, both in terms of space and time. The system uses takt-based scheduling as the scheduling type.

This is particularly suitable for takt-based production lines.

Integration

______________________________________________________________

SAP-System ______________________________________________________________



Line Design uses line resource as the resource type, as this supports the special type of capacity planning

on lines and takt-based scheduling. You define the production rates or takt times for takt-based

scheduling for the line resource.

The components Model mix planning and Planning matrix in the automotive process use the line

structure for logistics and planning functions, such as sequence optimization or the determination of the

requirements time for the components.

Scope of function

- You can carry out the planning on the aggregated level of the line. This means the line defines the

work-time capacity as well as the production rates and forwards these to the lower-level line

segments.

- You can reproduce the lines in a structure, by dividing them into line segments over as many

hierarchy levels as you want. On the lowest level you can divide the line segments further into work

packages, in order to reproduce various installation points within the line segment.

- You can enter the number of takts on the lowest level of the line segments. A takt is a physical area

in a line, in which the product remains for processing for the duration of the takt time. Therefore, the

number of takts determines the length of the line. If you have not divided a line into line segments,

you can also enter the number of takts for the total line.

- Within a line hierarchy you can put the line segments into a network sequence, using a

predecessor-successor relationship. In this network sequence you can also reproduce feeder lines,

for example, which are included in takt-based scheduling. For takt-based scheduling the system uses

the longest (critical) path through the line, which results from this network sequence.

- You can also insert buffers into the line structure in which orders can be stored temporarily. You

can also change the order sequence in a buffer.

- Lines, which are linked, but which have different operating times or takt times can be linked to a

line network. In this way you can group lines to a unit and plan orders for the total line network.

- The supply areas in flow manufacturing are places on the line, in which components are staged. You

can assign the supply areas to the line segments. This means that the line structure defines the

installation points of the components and indirectly also the staging area.

- In takt-based production the line structure determines the production flow. This means that you can

assign the line segments reporting points, at which you can later make confirmations.

- You can create a line balance for your production lines. In the line balance you assign the activities

from the iPPE structure to the line segments, so that the average work contents cover the given takt

time as well as possible. As an example for the model mix, you can enter a list of configuredmaterials and their quota to production.

You can create as many line balance versions as you want, to simulate different versions of the line

loading, and then to make this valid for certain periods.

By assigning activities to the line segments of jobs, you also indirectly determine the assignment of

the components to the exact installation points on the line. In this way, the planning matrix can

determine the exact requirements date for the components.

Restrictions

You cannot carry out lead-time scheduling via a routing in Line Design.

______________________________________________________________

SAP-System ______________________________________________________________




You can define the Customizing for iPPE Line Design in the unit iPPE-Line Design

1.1.6 BAPIs for Replicating iPPE Objects

Scope of Functions

SAP Automotive 2.0 offers BAPIs that receive the master data bills of material, routing, production lines,

and line balancing that already exist in non-SAP systems. The BAPIs replicate the master data in

integrated Product and Process Engineering and create corresponding iPPE objects in the SAP System.

Additional BAPIs send iPPE objects to non-SAP systems so that objects can be created as master data in

non-SAP systems.

The BAPIs below guarantee the performance of transaction PPE.

The individual BAPIs are:

- Replication of iPPE activities

- Save replicated iPPE activities

- Replication of iPPE components

- Save replicated iPPE components

- Replication of iPPE factory layout

- Save replicated iPPE factory layout

- Replication of iPPE line balancing

- Save replicated iPPE line balancing

See also

Online documentation for the following business objects:

- BUS1176 Component (Product and Process Engineering)

- BUS1179 Activity (Product and Process Engineering)

- BUS1182 Factory layout (Product and Process Engineering)

______________________________________________________________

SAP-System ______________________________________________________________



- BUS1183 Line Balancing (Product and Process Engineering)

1.1.7 Release Management (New)

Use

You can use release management during the development process of a new product to document the

development stages of the relevant parts (components), and to check if these components can be used in

development process. To do so, you use a release order and assign the components to the order. The

checks and the release occur within a workflow.

For example, you can first release the components of a product structure for production planning, then for

tool manufacturing and procurement, and then for production. Each release meets certain requirements

that you have defined for the checks in release management.

Release management is delivered for releasing component variants. You can define additional release

object types such as materials or vendors.

You can use the following functions:

- You can combine similar product parts in a release order, and have several users check the release

order.

- You can define release targets and checks to meet user-specific requirements.

- Objects that are processed in the release process, or those that have already been released can be

protected against changes. The attribute to be protected can be defined for each release object typeand target.

- The release status history for objects is stored in the system, and can be displayed in the Product

Designer and in the release orders.

- The release-relevant attributes are stored in the release orders, and can be evaluated for revision.


Carry out the following IMG activities:

Define Settings for Release Management

Create Number Range for Release Management

Assign Processor in Release Management

______________________________________________________________

SAP-System ______________________________________________________________



1.2.2 AP-MD-BF Basic Functions

1.2.2.1 AP-MD-BF-SYN Master Data Synchronization

1.2.2.1.1 Changes to the UI of the SAP Business Partner for Financial Services

Use

As of SAP ECC Enterprise Extension Financial Services 6.0 (EA-FS 600) the following changes

have been made to the dialog for the SAP Business Partner for Financial Services :

General Changes

- The Sales Area pushbutton in business partner maintenance is now called Sales and Distribution .

- You can switch company code, sales area, and purchasing organization several times within

business partner maintenance.

Customer/Vendor Integration

The transaction Create from Customer (FLBPD1) is now called Create Business Partner from Customer .

The transaction Link to Customer (FLBPD2) is now called Link Business Partner to Customer .

The transaction Create from Vendor (FLBPC1) is now called Create Business Partner from Vendor .

The transaction Link to Vendor (FLBPC2) is now called Link Business Partner to Vendor .

To make it easier to identify the data for customer/vendor master records in business partner

maintenance, the relevant data is displayed separately on new tab pages for the customer/vendor.

Changes to Customer Integration

Tab pages

Under General Data for the business partner you can find the new tab pages Customer: General Data

and Customer: Tax Data , and the renamed tab pages Customer: Additional Data (previously

Additional Customer Data ) and Customer: Uploading Points (previously Uploading Points ),depending on which BP role you have selected.

Under Company Code data for the business partner you can find the renamed tab pages Customer: Account Management, Customer: Payment Transactions, Customer: Correspondence,Customer: Insurance , and Customer: Status (previously Account Management, Payment Transactions, Correspondence, Insurance, Status ), and the new Customer: Withholding Tax tab

page, depending on which BP role you have selected.

Sections

General data

- Identification tab page (enhanced)

You can now store and delete several tax numbers for various tax number categories in a central

______________________________________________________________

SAP-System ______________________________________________________________



location for the business partner and the customer.

- Control tab page (changed)

- The Customer Assignment section is contained on the Customer: General Data tab page if

you have selected external number assignment for the customer.

If you have selected external number assignment for the customer, then this section contains

the customer number to be entered. The system transfers numbers entered in this section to the

Customer Number field in the new Customer Number section when you save the business

partner.

- The fields Authorization Group, Group Key, and Vendor are all displayed in the General Data section on the new Customer: General Data tab page. You can make a manual entry in

the Vendor field.

- Payment Transactions tab page (changed)The Payment Transactions section with the fields DME Indicator, Instruction Key, Alternative

Payer in Document, and Alternative Payer are now on the Customer: General Data tab page.

- Customer: General Data tab page (new)

The Marketing section is new and has the fields Nielsen Indicator, Regional Market, Customer

Classific., Hierarchy Assignment, Industry Code 1, Industry Code 2, Industry Code 3, Industry

Code 4, and Industry Code 5.

- Customer: Tax Data tab page (new)

The Customer: Tax Data tab page is new and has the sections:

- Tax Data

- Tax Categories

- Tax Calculation Brazil

- Tax Calculation Korea It also has corresponding fields for the customer.

Company code

- Header Data (Company Code-Dependent Screens) section (enhanced)

The Header Data (Company Code-Dependent Screens) general section is now called

Company Code .The processing of company code data has been improved. Within business partner maintenance you

can create, transfer, and - as long as you have not yet saved them - delete several company codes.

To do this, select Detail View Company Code . In the detail view you can also regulate for which

master data (business partner, customer, vendor) the company code is to be created.Under Switch Company Code you can switch to other company codes during processing.

In the Company Code section the vendor number for an assigned vendor is also displayed when

processing business partners in a customer-based business partner role.

- Customer: Account Management tab page (changed)

- In the Account Management section you can also process the Head Office field.

- The Default Data for Tax Reports section has been renamed Default Data for Tax Return .

- The Withholding Tax Types section with the corresponding fields is now on the new

Customer: Withholding Tax tab page.

______________________________________________________________

SAP-System ______________________________________________________________



Changes to Vendor Integration

Tab pages

Under General Data for the business partner you can find the new tab pages Vendor: General Data and Vendor: Tax Data , depending on which BP role you have selected.

Under the Company Code data for the business partner you can find the renamed tab pages Vendor: Account Management and Vendor: Payment Transactions (previously Account Management,Payment Transactions ), and the new tab pages Vendor: Withholding Tax and Vendor: Correspondence , depending on which BP role you have selected.

Sections

General data

- Identification tab page (enhanced)You can now store and delete several tax numbers for various tax number categories in a central

location for the business partner and the vendor.

- Control tab page (changed)

- The Vendor Assignment section is contained on the Vendor: General Data tab page if you

have selected external number assignment for the vendor.

If you have selected external number assignment for the vendor, then this section contains the

vendor number to be entered. The system transfers numbers entered in this section to the

Vendor Number field in the new Vendor Number section when you save the business partner.

- The fields Authorization Group, Group Key, and Customer are all displayed in the General Data section on the new Vendor: General Data tab page. You can make a manual entry in

the Customer field.

- The Trading Partner field is only displayed once for business partners in a vendor-based

business partner role. If necessary you can also assign the field to the vendor master record.

- Payment Transactions tab page (changed)

The Payment Transactions section with the ISR Number field is now on the Vendor: General Data tab page.

- Vendor: General Data tab page (new)

The Social Insurance section with the fields Social Insurance and Social Ins. Code is also new.

- Vendor: Tax Data tab page (new)

The Vendor: Tax Data tab page is new and has the sections:

- Tax Data

- Tax Office Responsible

- Tax Categories

- Tax Calculation Korea It also has corresponding fields for the vendor.

Company code

- Header Data (Company Code-Dependent Screens) section (enhanced)

The Header Data (Company Code-Dependent Screens) general section is now called

Company Code .

______________________________________________________________

SAP-System ______________________________________________________________



In the Company Code section the system also displays the customer number for an assigned

customer when processing business partners in a vendor-based business partner role.

- Vendor: Payment Transactions tab page (changed)

In the Automatic Payment Transactions section you can also set the Clearing with Vendor

indicator.

- Vendor: Correspondence tab page (new)

The Vendor: Correspondence tab page is new and contains the sections Dunning Data and

Correspondence as well as corresponding fields for the vendor.

- Vendor: Withholding Tax Types tab page (new)

The Vendor: Withholding Tax Types tab page is new and contains the Withholding Tax Types section as well as corresponding fields for the vendor.

See alsoFor more information about Customer/Vendor Integration, see Customer/Vendor Integration (Enhanced).

1.2.2.1.2 Customer/Vendor Integration (Enhanced)

Use

As of SAP ECC Enterprise Extension Financial Services 6.0 (EA-FS 600) Customer/Vendor

Integration for the business partner is part of Master Data Synchronization . Master Data

Synchronization can synchronize master data objects within an SAP System that are similar from abusiness perspective yet technically different. It ensures the seamless integration of various SAP

applications into business processes.

FI Customer/Vendor Integration for the business partner is now called Customer/Vendor Integration .The terms FI customer/customer and FI vendor/vendor can be used interchangeably within Master Data

Synchronization.

Customer/Vendor Integration has been enhanced with the following functions:

- Bidirectional synchronization (new)

Synchronization takes place in both directions between customer, vendor, and business partner.

When the business partner is updated the corresponding customer/vendor can be updated at the same

time. Likewise, when the customer/vendor is updated the corresponding business partner can also be

updated at the same time.

- Posting (changed)

- A new method is available for posting data in the customer/vendor master records. The posting

logic is not dependent on the interface.

- The method for posting both customer master records and vendor master records in

Customer/Vendor Integration is the same.

- The batch input for the vendor that was used to date has been completely removed.

For further technical information about the change in posting logic, see SAP Note 851444 .

- Data assignment (enhanced)

______________________________________________________________

SAP-System ______________________________________________________________



- CVI_ADJUST_ROLE_CUSTOMIZING Convert Role Customizing for Customer/Vendor Integration This report converts role Customizing to new applications, data sets, and field groups.

- CVI_ADJUST_TAX_DATA Synchronize Tax Data for Customer/Vendor Integration This report synchronizes tax data between the objects business partner, customer, and vendor. This

report prevents possible data losses incurred by overwriting tax data with another object.

You also have the option of carrying out the following reports:

- CVI_MIGRATE_CUST_LINKS Convert Assignment Table for Link Between BP and Customer

- CVI_MIGRATE_VEND_LINKS Convert Assignment Table for Link Between BP and Vendor

For more information about the reports, see the relevant report documentation and SAP Note 851445 .Customer-defined modifications

Due to the changes made in the architecture of the Customer/Vendor Integration you have to check any

customer-defined modifications and make any changes that are necessary.

The following enhancement spots with Business Add-Ins are available for enhancing Customer/Vendor

Integration:

- CVI_CUSTOM_MAPPER Data Assignment BP <-> Customer/Vendor/Contact Person

- CVI_DEFAULT_VALUES Defaults for Creating BP Data According to Customer/Vendor

- CVI_MAP_BANKDETAILS Data Assignment of Bank Details BP -> Customer

- CVI_MAP_CREDIT_CARDS Data Assignment of Payment Cards BP <-> Customer- CVI_MAP_TITLE Data Assignment of Form of Address from Customer/Vendor to BP

Customer-defined programs and search helps that refer directly to the assignment tables that are already

available have to be enhanced so that they include the new assignment tables. You also have to convert

any link postings that you have developed.

For detailed information about the necessary steps and enhancements that need to be adjusted, see SAP

Note 852991.


Implementation guide (IMG)

The synchronization is dependent on the Customizing settings for Master Data Synchronization that

you have to make.

You can find all of the required IMG activities in Customizing for Cross-Application Components by

choosing Master Data Synchronization->

- Synchronization Control

- Customer/Vendor Integration

In the Customizing for the area Synchronization Control you can activate or deactivate both the

synchronization of an individual object pair and the synchronization in a certain direction. The following

synchronization scenarios are supplied in the standard system:

______________________________________________________________

SAP-System ______________________________________________________________



- Synchronization of business partner to customer

- Synchronization of business partner to vendor

- Synchronization of customer to business partner

- Synchronization of vendor to business partner

In the Customizing for the area Customer/Vendor Integration you can execute all specific IMG

activities and Business Add-Ins (BAdIs) for the object pairs business partner/customer and business

partner/vendor.

For detailed information about the steps to be carried out, see the documentation for the IMG activities

and Business Add-Ins (BAdIs).

For more information about the new, changed, and deleted IMG activities and Business Add-Ins for

Customer/Vendor Integration, see Changes to the IMG for the SAP Business Partner for FinancialServices.

In addition to manually synchronizing Customizing settings for the business partner and the

customer/vendor you can automatically synchronize certain Customizing settings in certain

circumstances. The following reports are available for this purpose. These can be executed from within

the Synchronization Cockpit:

- Synchronize Customizing for Contact Person Attributes (CVI_MAPPING_CONTACTS)

- Synchronize Customizing for Legal Form and Legal Status (CVI_MAPPING_LEGAL_FORM)

Business Data Toolset (BDT)

The interface elements for the business partner in the Business Data Toolset (such as data sets, screens,

screen sequences, views, field groups, applications, and sections) have been restructured.

Note that customer-modified applications have to be adjusted to the changes in the Business Data Tool.

For more information about the changes in the Business Data Toolset and the steps to be carried out, see

SAP Note 852870 .

See also

For further information about changes to Master Data Synchronization, see the Release Notes for

additional components that use Master Data Synchronization.

For further information about Customer/Vendor Integration, see the SAP Library for the SAP Business Partner for Financial Services and additionally under SAP ERP Central Component -> Cross-Application Components -> Master Data Synchronization .

1.2.2.1.3 Changes to the IMG for the SAP Business Partner for FinancialServices

Use

As of SAP ECC Enterprise Extension Financial Services 6.0 (EA-FS 600), the structure of the

Implementation Guide (IMG) for the SAP Business Partner for Financial Services has changed. To

transfer these changes to the project IMGs, you need to regenerate the project IMGs.

______________________________________________________________

SAP-System ______________________________________________________________



Reassigned IMG Activities

The IMG activities Settings for Customer and Settings for Vendor are now in the new IMG area

Master Data Synchronization under Cross-Application Components-> Master Data Synchronization-> Customer/Vendor Integration-> Business Partner Settings-> Settings for Customer Integration and Settings for Vendor Integration .

The IMG area Settings for Customer Integration has been divided into the following new areas:

Field Assignment for Customer Integration

- Assign Keys

- Assign Attributes

You can find further settings for Financial Accounting that are relevant for synchronization, such asAccount Management, Account Balance Interest Calculation, Automatic Payment Transactions,Payment Data, Dunning Data, Specifications , in the new IMG area Master Data Synchronization by choosing Cross-Application Components-> Master Data Synchronization-> Customer/Vendor Integration-> Settings for Financial Accounting .

The areas Settings for Customer and Settings for Vendor and the corresponding IMG activities used

to be under SAP Banking-> SAP Business Partner for Financial Services-> Settings for Financial Services-> Communication .

Renamed IMG activities

- The IMG areas Settings for Customer and Settings for Vendor are now called Settings for

Customer Integration and Settings for Vendor Integration .

- In the new area Settings for Customer Integration , the IMG activity Define FI Customer Link to BP Role Category is now called Set BP Role Category for Direction BP to Customer.

- In the new area Settings for Customer Integration-> Field Assignment for Customer Integration-> Assign Keys , the IMG activity Assign Account Group to Grouping is now called

Define Number Assignment for Direction BP to Customer.

- In the new area Settings for Customer Integration-> Field Assignment for Customer Integration-> Assign Attributes , the IMG activity Map Industries is now called Assign

Industries.

- In the new area Settings for Vendor Integration , the IMG activity Define FI Vendor Link to BP

Role Category is now called Set BP Role Category for Direction BP to Vendor.

- In the new area Settings for Vendor Integration-> Field Assignment for Vendor Integration-> Assign Keys , the IMG activity Assign Account Group to Grouping is now called Define

Number Assignment for Direction BP to Vendor.

- In the new area Settings for Vendor Integration-> Field Assignment for Vendor Integration-> Assign Attributes , the IMG activity Map Industries is now called Assign Industries.

New IMG Activities

SAP Business Partner for Financial Services

______________________________________________________________

SAP-System ______________________________________________________________



- Area Settings for Financial Services-> General Settings-> Enhancement Options-> Easy Enhancement Workbench-> Maintain System Landscape

Master Data Synchronization

- Area Customer/Vendor Integration-> Business Partner Settings-> Business Add-Ins (BAdIs)->

- BAdI: Data Assignment BP <-> Customer/Vendor/Contact Person

- BAdI: Data Assignment of Bank Details BP -> Customer

- BAdI: Data Assignment of Payment Cards BP <-> Customer

- BAdI: Data Assignment of Form of Address from Customer/Vendor to BP

- BAdI: Defaults for Creating BP Data According to Customer/Vendor- Area Customer/Vendor Integration-> Business Partner Settings-> Settings for Customer

Integration-> Define BP Role for Direction Customer to BP

- Area Settings for Customer Integration-> Field Assignment for Customer Integration-> Assign Keys->

- Define Number Assignment for Direction Customer to BP

- Area Settings for Customer Integration-> Field Assignment for Customer Integration-> Assign Attributes->

- Activate Assignment of Contact Persons

- Assign Department Numbers for Contact Person

- Assign Functions of Contact Person

- Assign Authority of Contact Person

- Assign VIP Indicator for Contact Person

- Area Settings for Customer Integration-> Field Assignment for Customer Integration-> Assign Attributes->

- Assign Marital Statuses

- Assign Legal Form to Legal Status

- Assign Payment Cards

- Area Customer/Vendor Integration-> Business Partner Settings-> Settings for Vendor Integration-> Define BP Role for Direction Vendor to BP

- Area Settings for Vendor Integration-> Field Assignment for Vendor Integration-> Assign Keys-> Define Number Assignment for Direction Vendor to BP

1.2.2.1.4 Synchronization Cockpit (New)

Use

______________________________________________________________

SAP-System ______________________________________________________________



From SAP ECC 6.0, SAP_APPL 600 you can use the Synchronization Cockpit in the context of Master

Data Synchronization in order to prepare, carry out and check initial mass synchronization between

master data objects in an SAP system.


You can start the Synchronization Cockpit in Customizing of the Cross-Application Components

under Master Data Synchronization -> Synchronization of Mass Data -> Execute Synchronization Cockpit .

See also

For more information about the Synchronization Cockpit, see the SAP Library under SAP ERP Central

Components -> Cross-Application Components -> Master Data Synchronization -> Synchronization

Cockpit .

1.2.2.1.5 Master Data Synchronization (New)

Use

From SAP ECC 6.0, SAP_APPL 600, Master Data Synchronization allows you to integrate master data

objects that are similar from a business point of view, but different from a technical point of view (for

example, Customer Master and Business Partner) in an SAP system. It ensures business processes run

smoothly through the simultaneous synchronization of master data, meaning that all processes can access

the same data at any time.

Technically speaking, Master Data Synchronization replaces the current solution for integrating the

Customer Master, Vendor Master and Business Partner. In addition, Master Data Synchronization now

also allows the integration of the product master with the material master or the service master.

Master Data Synchronization is carried out from the processing functions of the individual master data

objects. You can use the Synchronization Cockpit for initial mass synchronization between two master

data object types.

Effects on Data Transfer

From a functional point of view, Master Data Synchronization is a form of data exchange within the

system, that takes place directly and synchronously via the interfaces of the individual master data

objects. It does not use the SAP Exchange Infrastructure, with the exchange of B2B or A2A messages. In

this respect, Master Data Synchronization cannot be employed across system boundaries.

Effects on System Administration

If master data objects, which are defined as source objects in a synchronization process, already exist in

the system, then they can first be synchronized in an initial synchronization with the defined target

objects, using the Synchronization Cockpit. If Master Data Synchronization is active, then users need

______________________________________________________________

SAP-System ______________________________________________________________



authorization to maintain all those master data objects that can be synchronized using Master Data

Synchronization. If, for example, synchronization between the Business Partner and the Customer Masteris active in the system, then the processor must be authorized to maintain the Business Partner and the

Customer Master.


In order to be able to use Master Data Synchronization, you must first set and activate the Master Data

Synchronization in the relevant Customizing.

For more information about Master Data Synchronization, see the Implementation Guide (IMG) of the

Cross-Application Components under Master Data Synchronization.

See also

For more information about the Synchronization Cockpit, see the notes 852866 and 857344, as well as

the SAP Library under SAP ERP Central Components -> Cross-Application Components -> Master Data

Synchronization -> Synchronization Cockpit .

1.3 AP-PRC Pricing & Condition Technique

1.3.1 AP-PRC-CON Konditionstechnik

1.3.1.1

1.3.1.2

1.3.1.3

1.4 AP-TTE Transaction Tax Engine

1.4.1

______________________________________________________________

SAP-System ______________________________________________________________



Creating Line Structures with Alternatives

Use

As of Release DI 4.6C2, you can create line networks, which consist of several production lines

that can be used as alternatives to each other. Various products can run along these productionlines. You can depict the possible routes for each product. Two new elements have been added to

the line network to make this possible:

Group of alternative lines

Sometimes a product can be produced on several production lines that have the same

function, and not just on one line. During planning, you must be able to state which

alternative lines are to be used to produce a particular product. You can use the new nodetype, the group of alternative lines, to group together alternative lines. This node type

enables you to manually reschedule an order from one line to an alternative line in

interactive sequence planning.

Part of line network

Several products can be produced in a line network. They run partly along the same

production lines or groups of alternative lines. You must be able to view the situation onall the production lines to be able to implement a correct model mix planning for all the

products that share a line network. The line network is now a cross-product line network.

The part of line network has been introduced to help you identify which parts of the line

network a product can run along. You create a part of line network as an alternative in theline network and select which production lines are to belong to it.

Example

A line network consists of body shop, paintwork, and final assembly. The body shop consists of

two production lines, body shop 1 and body shop 2. These two production lines can be used asalternatives to each other. The final assembly also consists of three final assembly production

lines, which can be used alternatively. There is only one production line for the paint work,

which receives parts from both of the body shop production lines. All of the production lines are

divided into line segments.

The procedure for creating this line structure would be as follows:

1. You create the necessary line elements:

o Group of alternative lines 'body shop'

o Group of alternative lines 'final assembly'



o Line 'paintwork'

o Line 'body shop 1'

o Line 'body shop 2'

o Line 'final assembly 1'



o All the subordinate line segments.

1. You create the alternatives. On the 'Alternative Lines' tab page for the group of

alternative lines 'body shop', enter both the production lines 'body shop 1' and 'body shop

2'. Do the same for the group of alternative lines 'final assembly'.2. You maintain the hierarchy relationships as follows:

Enter the line network on the 'Relationships' tab page for the groups of alternative lines.You assign line segments to the lines in the same way.

1. On the 'Part of Line Network' tab page for the line network, you create the alternatives 1and 2, with a description of your choice. Save your entries. Double click on the part of

line network 1 in the structure tree. A list of the lines and buffers in the line network is

displayed. Select a line and a buffer, if applicable.2. Maintain sequences (predecessor/successor relationships) between elements that are

assigned to the same higher-level element.

creating line structures with alternatives

Documents