Kontakt

Ansicht
Dokumentation

FINS_CFIN_EBM - Enhanced Business Mapping

FINS_CFIN_EBM - Enhanced Business Mapping

CL_GUI_FRONTEND_SERVICES - Frontend Services   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.
SAP E-Book

You can map customer-defined fields for the accounting interface.

If you need to map new (that is, customer-defined) fields for the accounting interface, proceed as follows:

  1. Verify the mapping structure.
Verify that the relevant fields (and related context fields) are part of the (same) mapping structure.
All mapping structures, which are supported in Central Finance, can be found in table FINS_CFIN_MDGTS. The relevant DDIC-Structure is listed in column Type Name (STRUCTURE_TYPE).
  1. Check field assignment to mapping entities.
Make sure that the field has not yet been mapped using a mapping entity. To do so, go to transaction SE16N and select the field in view V_FINS_CFIN_MAPS and in view V_FINS_CFIN_MAPC using the fields FIELD_NAME and STRUCTURE_NAME (which corresponds to FINS_CFIN_MDGTS-MAPPING_STRUCTURE).
  1. Check existence of a suitable mapping entity.
If the field has not yet been mapped using 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.
  1. Is it a code or a business object ID?
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.
  1. Business Object ID already defined?
If it is a business object ID, proceed with activity Introduce a new Business Object Identifier(described below).
  1. Global Data Type (GDT) already defined?
If it is a code, proceed with activity Introduce a new Global Data Type(described below).

Introduce a new Business Object Identifier

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

  1. Before you introduce a new identifier, check Define Object Identifiers to see whether the object ID type that you want to map exists.
  2. If the Object ID Type does not exist, proceed as follows:
    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.
  1. Define Object Nodes (if required).
For each object node, you must maintain the object node type and object node type description. (Typically any BO has at least one node called "Root" which holds the relevant IDs for identification of the business object.)
  1. Define Object Identifiers (if required).
For each object identifier, you must specify the object ID type, description of object ID type, BO type, object ID constant name, object node type, and further attributes as required.
  1. 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.
  1. 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).
  1. Once you have the object identifier defined, you can create the new Mapping Entity via activity Define Mapping Entities (Enhanced Configuration) .Follow chapters Define a Mapping Entity for Code Mapping and Define Mapped Fields (Customer System).

Introduce a new Global Data Type (GDT)

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

  1. Before you introduce a new GDT, check Maintain Value Mapping to see whether the code that you want to map is already represented by an appropriate GDT.
  2. If the GDT does not exist, proceed as follows:
    1. Create a context structure.
Check the code definition. If the code is defined only within a context (for example, payment methods are defined per country/region), create a DDIC structure using transaction SE11 for the context attributes. Otherwise the context structure is not needed.
  1. Create a code list provider class using transaction SE24.
  2. Define a data element-based (or structure based) GDT via activity Maintain Value Mapping.
  • Once you have the GDT defined, you can create the new Mapping Entity via activity Define Mapping Entities (Enhanced Configuration). Follow chapters Define a Mapping Entity for Code Mapping and Define Mapped Fields (Customer System).






    • ABAP Short Reference   Addresses (Business Address Services)  
    This documentation is copyright by SAP AG.

    Length: 6684 Date: 20240523 Time: 202511     sap01-206 ( 85 ms )