Field descriptions - Intergraph Smart Materials - Version 2020 (10.0) - Administration & Configuration - Hexagon

Intergraph Smart Materials Integration (2020)

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

SAP Interfaces Block

In this block, the Interfaces will be selected that were defined in SAP 10.01 and for which requisition transfer jobs shall be defined.

Interface. Name of the SAP interface.

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

SAP Req Transfer Job Block

Enter a unique job name here and save the record to be able to select the requisitions to transfer. After that, click the Transfer Online button to start the requisition data transfer.

Job. Name (code) of the transfer job.

Short Desc. Short description of the transfer job.

Description. Long description of the transfer job.

Job Start User. User who starts the job.

Job Status. Status of defined job.

Job Start Date. Job start date.

Job Finish Date. Job finish date.

Log File. Log file name on the database server.

Job Return Code. The return code of the job.

Job Summary. The summary of the finished job. Shows information about transferred requisitions.

Start. Starts the transfer job.

Show Protocol. Displays the log file.

SAP Requisitions Block

After saving the job information in the SAP Req Transfer Jobs block, the job status changes to the "ready to run" status. Now the user can choose the requisitions that should be transferred to SAP. For that, all approved requisitions that have the project default ZI_SAP_INTF defined attribute attached will be displayed in this block.

All unsuccessful transferred requisitions will be displayed.

In both cases, the attribute value must match the name of the interface (interface_code) or be Null. Otherwise, the requisition will not be shown.

Engineering Requisition. Name (code, number) of the requisition. The name of the engineering requisition can be any valid string (in uppercase letters, not exceeding 50 characters). The name must be unique in combination with the supplement, purchase indicator, and origin within a project.

Suppl. Supplement number of the engineering requisition.

Purchase. This indicator shows whether the line items of this engineering requisition can be used for both purchase orders and inquiries or only for inquiries.

If this check box is not checked, the engineering requisition can only be used for inquiries.

Origin. Code for engineering requisitions and purchase orders that represents the office that is responsible for the information.

Plant. Value of the SAP_PLANT attribute.

Transfer to SAP. Check the check box for all requisitions you want to transfer to SAP. You can only transfer requisitions that have a valid plant (defined for the interface on SAP 10.08). The interface checks to see whether all the material inside the requisition is successfully transferred to SAP already. If not, the requisition cannot be selected for the transfer.

A successful data transfer to SAP means only a successful creation of the IDocs data in either XML format or in the XI-interface tables and says nothing about the processing result by SAP.

SAP transfer using XML files

The following files are created when the transfer type XML has been selected on SAP 10.01:

PRECQR_jobnr_seqnr.XML

XML file of IDOC PRECQR

PRECQR _jobnr_seqnrN.XML

XML file of IDOC type PRECQR for SAP without line feed and leading blanks (only this file will be transmitted by ftp)

The import of the XML files into SAP is described in a separate section.

SAP transfer using database tables

The SAP transfer for material and requisition data now allows you to use the following transfer modes:

  • Generation of XML files

  • Export into database tables (NEW !)

Use SAP 10.01 SAP Interface Parameter to select the desired mode.

Interface tables will be created the first time the export for database tables is started .

The tables are created in the M_SYS schema.

The system will generate a table for each segment defined on SAP 10.03 SAP IDocs for the SAP version defined on SAP 10.01. The name of the tables will be ‘XI_’+<Segmentname>.

The tables (called from now on XI-tables) will include as columns the fields defined for the segment.

Before each run of the export for database tables, a check is performed whether the table definitions still match the IDOC definitions on SAP 10.03. If this is not the case, then missing fields will be added as new columns to the table. Also, the column size will be increased accordingly.

The ID field of each table is used to identify all segments of an IDOC.

Additional fields ID1, ID2, ID3 (depending on the IDOC definition) represent the sequence and hierarchy of the IDOC because the IDOC information is distributed over different tables.

The fields always start with 1 and are increased for each segment on the same hierarchy level.

Example 1

1 1

1 2

2 1

2 1 1

2 2

2 2 1

To control access to the tables, you can use the column STATUS. This is filled by default with the value ‘01’.

A new user SAP_XI will be created the first time the transfer for tables is started. This user will have access to all interface tables.