Scribd
Upload
166 views

Define COPA Mapping: Requirements

This document describes how to define mappings between characteristics and value fields in the source system and the Central Finance system for COPA documents during replication. It involves mapping operating concerns, characteristics, and value fields between the two systems. It also describes how to update mappings if the structure is changed and how the central finance system determines values during replication based on the mappings.

Uploaded by

GK SK
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
166 views

Define COPA Mapping: Requirements

This document describes how to define mappings between characteristics and value fields in the source system and the Central Finance system for COPA documents during replication. It involves mapping operating concerns, characteristics, and value fields between the two systems. It also describes how to update mappings if the structure is changed and how the central finance system determines values during replication based on the mappings.

Uploaded by

GK SK
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Define COPA Mapping

Send feedback

In this Customizing activity, you can maintain mappings for COPA-related characteristics and value fields
between the source system and the Central Finance system.

You can map several operating concerns in the source system to each operating concern in the Central
Finance system.

You can define mappings for the characteristics and the value fields for each pair of source or central
operating concerns.

During the replication of COPA documents, the Central Finance system determines the value of each
characteristic or value field of a document based on the corresponding field in the source document and
according to the mappings that you configure in this activity.

If the customized characteristics or value fields are changed in either the source system or the Central
Finance system, you can use the button “Sync Structure” to update the previously configured mappings to
reflect the most recent changes.

Requirements

The authorization object S_DEVELOP is assigned to your user.

Standard Settings

When you create a new set of mappings, the system proposes a default set of mappings based on a
preliminary examination of the characteristics or value fields being mapped. You can then further customize
the proposed mappings.

NoteThis acivity is located under Central Finance  Central Finance: Target System


Settings  Mapping  COPA Mapping  Define COPA Mapping

PreviousNext

Introduce a New Business Object Identifier


Send feedback

Use
If you need to map new (that is, customer-defined) fields of the accounting interface proceed as follows:
1. Make sure that the field has not yet been mapped via a mapping entity. To do so, go to
transaction SE16N and select in view V_FINS_CFIN_MAPS and in view V_FINS_CFIN_MAPC the field via
the fields FIELD_NAME and STRUCTURE_NAME.

2. If the field has not yet been mapped via a mapping entity, check whether an appropriate mapping entity
already exists. If so, you only need to assign the new field to the mapping entity.

3. If an appropriate mapping entity does not yet exist, you need to create a new mapping entity. In order to do
so you have to determine whether the mapped data represents a business object ID or a code.

a. If it is a business object ID, check MDG key mapping to see whether the object ID type that you want to
map already exists. If not, create this object ID type as described in the procedure below.

b. If it is a code, check MDG value mapping to see whether an appropriate global data type has already been
defined. If not, create it as described in the procedure below.

4. Now you can create the new mapping entity. Details are described in the specific procedures below.

Procedure
To map new ID fields of the accounting interface, you can introduce a new business object identifier.

Checks

Before you introduce a new identifier, check MDG key mapping to see whether the object ID type that you
want to map exists. If so, create the mapping entity. If the object ID type does not yet exist, proceed as
follows:

Configuration in MDG

The following activities are located in Customizing for MDG under Cross-Application


Components   Processes and Tools for Enterprise Applications  Master Data Governance  Central
Governance  General Settings  Key Mapping  Enhance Key Mapping Content

1. Define Business Objects (if required)

For each business object, define a BO type (customer namespaces are Y* and Z*), a description, and a
constant name.

Once you have defined a BO identifier (which you do in the next step), you should also enter the Object ID
Type for Key Structure Access.

2. Define Object Nodes (if required)

For each object node, you must maintain the object node type and object node type description.

3. Define Object Identifiers (if required)

For each object identifier, you must specify the following values:

• Object ID Type

• Description of Object ID Type

• BO Type

• Object ID Constant Name


• Object Node Type

• Further attributes as described in the documentation of the IMG activity

4. Assign Key Structures to Object Identifiers

Specify the key structure for the object identifier you have just defined.

As a prerequisite, you must find or create the key structure as a data type of the category structure via
DDIC (transaction SE11). Save and activate the structure.

5. Assign Business Objects to Main Contexts

Enter the BO type and pick the relevant Main Context from the value help (in most cases you can use the
context SAPdefaultMapping).

Define Mapping Entity

1. Go to transaction SM34 and call view cluster VC_FINS_CFIN_MDG. In the field Mapping Entity, enter the


object ID.

2. In the field Object ID, use value help to choose the object ID you defined in the previous step.

3. Select the new item and maintain Define Mapped Fields (Customer):

4. Enter the structure using the value help choose Enter.

5. Enter the field name and choose Enter.

6. If required, enter the Context Field 1and if applicable also Context Field 2.

7. Save your entries.

Introduce a New Code

To map further code fields of the accounting interface, you can introduce a new code.

Checks

Before you introduce a new code, check MDG key mapping to see whether the code that you want to map
exists. If you find an appropriate code, proceed with the step Define Mapping Entity. Otherwise, proceed
as follows:

Create Context Structure

Check the code definition. If the code is defined only within a context (for example, payment methods are
defined per country) create a DDIC structure for the context attributes.

Create Code List Provider Class

1. Create a new class in the customer namespace and add the interface IF_ESF_CODE_LIST_PROVIDER.

2. Implement the methods INIT, RETRIEVE_CODE_DESCRIPTIONS,


RETRIEVE_CODE_LIST and RETRIEVE_CODE_VALUES.

3. Activate the class.

4. Test the class using transaction SE24, F8:


a. Execute method IF_ESF_CODE_LIST_PROVIDER~INIT .

b. Execute method IF_ESF_CODE_LIST_PROVIDER~RETRIEVE_CODE_LIST.

Parameter IN_LANGUAGE_CODE must be filled to yield a result. If the code has a context then also fill the
context value in parameter IN_LIST_ID.

c. Execute and check the result.

Define Data Element-Based GDT

Use the Customizing activity Maintain Value Mapping to define the new GDT.

Choose object type Data Element and enter the DDIC data element of your code as global data type. If the
code is client-dependent, set the respective indicator. If the code has a context, enter the context structure.
Enter the code list provider class as Input Help. Save the GDT.

Maintain mapping data (by choosing the Navigation button) and check the value help of the field Internal
Code Value.

Define Mapping Entity

In the activity Define Mapping Entities (Enhanced Configuration), make the following entries:

• Mapping Entity: GDT (Data Element)

Use the customer namespace Y* or Z*.

• Type: Data Element

• Global Data Type: GDT (Data Element)

Select the newly created item and maintain Define Mapped Fields (Customer): Enter the structure using
the value help and choose Enter. Enter the field name and choose Enter. If required enter the Context
Field 1.

PreviousNext

You might also like