SAP 10.05 Master Data Mapping - Intergraph Smart Materials - Version 10.1 - Administration & Configuration - Hexagon

Intergraph Smart Materials Integration (10.1)

Language
English
Product
Intergraph Smart Materials
Subproduct
Classic
Search by Category
Administration & Configuration
Smart Construction Version
8
Smart Materials/Smart Reference Data Version
10.1

This screen is a detail screen for SAP 10.01 Interface Parameters; that is, the values are SAP interface specific. All the SAP master data features for the idents that are to be transferred by the interface are mapped on this screen.

The IDocs fields with which the information is transferred are mapped on this screen. Each Master Data field in SAP corresponds to a field in the IDoc data structure. The user must have accurate knowledge about the IDocs field names and the internal SAP master data fields.

The IDoc fields that are available for selection in the LOV (IDoc Field) correspond to the fields from IDoc MATMAS03 (SAP master data), which are flagged on screen SAP 10.03 SAP IDocs as plant-independent master data.

The interface setting variable MATMASIDOD defines which MATMAS IDoc of the respective interface is active. The name of the desired MATMAS IDocs must be assigned to this variable (refer to the description of A.70.11 Interface Settings). This is important if a user-modified MATMAS IDoc is used besides the delivered MATMAS03 IDoc.

The IDoc fields’ values are defined by the filter, which is set up by the Group, Part, Commodity Code, and Ident Code fields. This means that IDoc field assignments can be handled globally (without any filter entries) or respectively grouped (by filter entry).

While mapping the IDoc fields, the sequence has to be considered, particularly if exceptions shall be set up. An example is if the value for the IDoc field MAKTX (SAP short description) will be determined by a CIP function "CIP1". All idents belonging to the group "Pipes" will be exceptions and the Idoc field MAKTX will be set up by the CIP function "CIP2". The first step is to declare all exceptions by assigning the smallest sequence numbers to the smallest granularities (idents).

CIP functions and ident functions are not part of the delivery and they will not be maintained by Intergraph.

Field Descriptions

Block 1: SAP Interfaces - In this block, the interfaces that were defined on SAP 10.01 are selected. These interfaces are the interfaces for which the SAP IDoc master data fields will be mapped.

Interface - Name of the SAP interface.

Short Desc and Description – Language-dependent description of the SAP interface.

Block 2: SAP Master Data - In this block, the non-dependent SAP master data IDoc fields (Master Data check box on SAP 10.03, IDoc Fields block) will be mapped to Smart Materials information. This can be fixed values, ident attributes, CIP functions, or ident functions.

Seq - Order sequence for the order of the mapped IDoc master data fields. This sequence is particularly important if an IDoc field will be global and for example, assigned to a specific ident, which is contained within the "generality". The value that is mapped first will be assigned to the IDoc field, so it is very important to assign the first (lower sequence number) the appropriate exceptions and only then (higher sequence number) the ident groups that are higher in granularity.

Group - Group Code Filter. By selecting a group code, the assignment of the mapped IDoc fields is carried out only for those fields that belong to this group.

Part - Part Filter. By selecting a part code, the assignment of the mapped IDoc fields is carried out only for those fields that belong to this group.

Commodity Code - By selecting a commodity code, the assignment of the mapped IDoc fields is carried out only for those fields belonging to this group.

Ident - Ident filter. By selecting an ident, the assignment of the mapped IDoc fields is carried out only for the chosen ident.

Segment - Displays the segment belonging to the IDoc field.

IDoc Field - The IDoc field that will be mapped must be selected. There is an LOV containing any plant-independent IDoc fields of the valid MATMAS IDoc, which means any IDoc fields defined on SAP 10.03 as master data fields (Master Data check box).

Value Type - The values of the IDoc fields will be determined in different ways. You can choose among the following value types:

  • Fixed - Features with a fixed value can be transferred to SAP. This means that the value in the Value/Content field will be actually assigned to the IDoc field.

  • Ident - All the Smart Materials ident attributes can be assigned to IDoc fields, that is, commodity attribute and/or object parameter details (geometry). If you select "Ident" as the Feature type, an LOV in the Value/Content field will display all the available Smart Materials ident attributes. The value of the ident attribute will be assigned to the respective IDoc field.

  • CIP function - You can define any CIP function or ident function to use here. The CIP function must return a string (VARCHAR2) as the return value, which then will be transferred as the value to SAP. The first input parameter of the CIP function is the ID of the SAP interface, so the CIP may do different things depending on the SAP interface.

The CIP functions must have the following syntax:

FUNCTION m_pck_sap_custom.<functionname>

( p_interface_id IN m_interfaces.interface_id%TYPE,

,p_ident IN m_idents.ident%TYPE

,p_nls_id IN m_nls.nls_id%TYPE

,p_sp_id IN m_sap_plants.sp_id%TYPE )

return varchar2;

The return value of the CIP function will be assigned to the respective IDoc field.

  • Ident function - Can be defined on Smart Materials screen A.60.13. The Ident field is transferred and the function returns a character (VARCHAR2) value, which then will be transferred to SAP. In this way, it is possible to use any valid ident function to transfer its return value to SAP. If "CIP" is selected as the attribute type, an LOV in the Value / Content field displays all the available Smart Materials ident functions or CIP functions.

Value/Content - This field contains the value of the IDoc field, but it will be interpreted depending on the Value Type field.

Multi Language -The Multi Language check box defines if the corresponding attribute is to be managed in a multi-lingual way. In most cases, this applies to descriptive IDoc fields (MAKTX field in segment MAKTM, TDLINE field in MTXLM Segment).