Use Export Specification Maintenance (36.8.1.2) and Import
Specification Maintenance (36.8.1.3) to identify particular documents and to set document-specific parameter values for exporting and importing. For exports, you can define interface control, document content, data mapping parameters, messaging, and miscellaneous parameters. For import, you define interface control, data mapping, and miscellaneous parameters.
Note When the specification is associated with a system ID that is not registered as an external application—indicating a domain within the current database—the frames for updating data mapping, messaging, and miscellaneous parameters for export specifications do not display. These values are not used for synchronizing data among local domains.
¶ See “Register Domains” on page 144.
When specifications are associated with registered applications, many fields default from the values you specify in Register External
Application. These defaults do not exist when creating specifications for use with domains in the same database.
For registered applications, you may be able to import and export documents without a specific specification in limited cases. In these cases, the values specified in Register External Application are used as is. Matching Specifications to Documents
You can use up to five values to define an import or export specification: document standard, document type, document revision, application ID, and trading partner ID. The only required field is the document type. The system uses the following logic to find a specification to apply to a document:
1 It looks for one with an exact match for document standard, document type, document revision, application ID, and trading partner ID. 2 It looks for one with matching document standard, document type,
document revision, application ID, and a blank trading partner ID. 3 It looks for one with matching document standard, document type,
document revision, and blank application and trading partner IDs. This lets you set up generic specifications that can apply to all documents of a certain type (and optional standard and revision) regardless of the particular application or trading partner associated with a document.
¶ See “Copy Import and Export Specifications” on page 160.
This can be useful when you set up specifications for synchronizing data among domains in separate databases. You can define a generic
specification for a particular table (identified by the document type) and leave the application ID blank. Then copy this record to each affected domain using Export/Import Specification Copy. This lets you quickly set up similar export and import specification records.
Required Specifications
Import specifications are required when:
• A document type must be routed to a specific, non-default MFG/PRO program for processing.
• A document type must be mapped by a specific, non-default mapping procedure or mapping specification.
Export specifications are required when:
• A document type must be associated with a specific synchronization profile.
• A document type must be mapped by a specific, non-default mapping procedure or mapping specification.
Defining specifications for unique export documents supports flexibility in data synchronization. For example, you can:
• Export synchronization events for different tables to different destinations.
• Export synchronization events for different fields in specific tables to different destinations.
Register Export Specifications
Use Export Specification Maintenance to:
• Create an export specification for each synchronization document type to be exported to each domain.
• Associate a synchronization profile with each synchronization document type.
• Optionally associate a synchronization profile with a system ID, registered application, or destination list.
Accept the Q/LinQ defaults except where noted.
Fig. 4.16
Export Specification Maintenance (36.8.1.2)
Application or Destination List ID. Enter one of the following: • The system ID of another domain in this database as defined in
Q/LinQ Control (36.8.24)
• The ID of a domain in this or an external database as it is defined in Register External Application (36.8.1.1)
• The name of a destination list as defined in Destination List Maintenance (36.8.8)
Leave blank if you want this specification to apply to all documents of a certain type, standard, and revision without regard to the associated application.
Document Standard. Enter a user-defined name such as sync_docs so that synchronization activity and documents can be easily segregated from other Q/LinQ documents and activities. This field is validated against generalized codes defined for field esp_doc_std.
Document Type. Enter a user-defined name for the type of data that is being synchronized. Use names that reflect the type of data, such as pt_part for item numbers, to facilitate browsing, reporting, and tracking specific data elements.
Document Revision and Trading Partner ID can be left blank. If they are used, Document Standard, Document Type, Document Revision, and Trading Partner ID must be a unique combination of values.
Fig. 4.17 Export Specification Maintenance, Interface Control Parameters
Default E-mail User ID, E-mail Level. Enter data for fields, as needed. For registered application IDs, these fields default from Register External Application.
Publishing Enabled. Enter Yes when the export specification is ready to be used by Q/LinQ. Enter No for Q/LinQ to ignore this
Fig. 4.18 Export Specification Maintenance, Document Content
Profile ID. Enter the name of a synchronization profile as it is defined in Synchronization Profile Maintenance (36.8.22.1). Only one profile can be associated with an export specification.
Publish on Table Update. Enter Yes to create export documents for the specified profile whenever a record in the associated table is updated. This is event-driven, automatic data exporting.
For batch-only data synchronization, enter No and use
Synchronization Mass Export (36.8.22.8) to create export documents for a specified profile.
Note The following frame displays only when you are setting up export specifications for synchronizing data between databases. If the
Application ID specified is a domain system ID, this frame is not needed.
Fig. 4.19 Export Specification Maintenance, Messaging and Miscellaneous Parameters
Precede Data with Tags. Enter Yes to embed document control tags in front of the actual data when using the stream or messaging APIs to send documents to external databases. Control tags are always included when sending documents to a file.
Access Code/Path. Specify the name of the domain in the external database to receive messages based on this export specification.
Note If you specified a destination list as the Application ID, any value you specify in this field is ignored. Q/LinQ uses the value specified in Register External Application for each application in the list.
Register Import Specifications
Use Import Specification Maintenance (36.8.1.3) to register each inbound synchronization document type. Accept the Q/LinQ defaults except where noted. Fig. 4.20 Import Specification Maintenance (36.8.1.3) Tip Destination lists cannot be used with import documents.
Application ID. Enter the name of an external MFG/PRO domain as it is defined in Register External Application (36.8.1.1) or the system ID of another domain within the current database defined in Q/LinQ Control (36.8.24).
Leave blank if you want this specification to apply to all documents of a certain type, standard, and revision without regard to the associated application.
Document Standard. Enter a user-defined name such as sync_docs so that synchronization activity and documents can be easily segregated from other Q/LinQ documents and activities.
This field is validated against codes defined in Generalized Codes Maintenance for field esp_doc_std.
Document Type. Enter a user-defined name for the type of data that is being synchronized. Use names that reflect the type of data, such as pt_part for item numbers, to facilitate browsing, reporting, and tracking specific data elements.
Document Revision and Trading Partner ID can be left blank. If they are used, Document Standard, Document Type, Document Revision, and Trading Partner ID must be a unique combination of values.
Fig. 4.21 Import Specification Maintenance, Interface Control Parameters
In the Interface Control Parameters frame, set up incoming processing and e-mail notification parameters.
Default E-mail User ID, E-mail Level. Enter data in these fields as needed or accept the defaults specified for the database in Register External Application.
¶ See Table 4.3 on page 159 for a list of MFG/PRO programs.
MFG/PRO Destination Procedure. Enter the name of the MFG/PRO program to call to process the data from the imported synchronization document as an MFG/PRO transaction.
Process Through User Interface. Enter Yes to invoke the destination procedure through the CIM Interface. Yes is required for
synchronization. Fig. 4.22 Import Specification Maintenance, Data Mapping Parameters
In the Data Mapping Parameters frame, specify the data mapping procedure from Table 4.3. Select the procedure that represents both the destination procedure and the table for the imported data type.
Table 4.3
Synchronization Data Mapping Programs
Destination Procedure Supported Tables Mapping Procedure Name
adcsmt.p ad_mstr qqadmp.p cm_mstr qqcmmp.p adlsmt.p ls_mstr qqlsmp.p adrtmt.p ad_mstr qqadmp.p
ls_mstr qqlsmp.p adstmt.p ad_mstr qqadmp.p
cm_mstr qqcmmp.p advnmt.p vd_mstr qqvdmp.p
ad_mstr qqadmp.p ls_mstr qqlsmp.p bmmamt.p bom_mstr qqbommp.p bmpsmt.p ps_mstr qqpsmt.p csmsmt.p cs_mstr qqcsmp.p fcfsmt01.p fcs_sum qqfcsmp.p glenmt.p en_mstr qqenmp.p glacmt.p ac_mstr qqacmp.p glcalmt.p glc_cal qqglcmp.p glcd_det qqglcdmp.p glsbmt.p sb_mstr qqsbmp.p cr_det qqcrmp.p glccmt.p cc_mstr qqccmp.p cr_det qqcrmp.p gpcmmt.p cd_det qqcdmp.p icsimt.p si_mstr qqsimp.p icstmt.p is_mstr
isd_det
qqismp.p qqisdmp.p mccuacmt.p acdf_mstr qqacdfmp.p mccumt.p cu_mstr qqcump.p mcexrmt.p exr_rate qqexrmt.p mgcodemt.p code_mstr qqcodemp.p ppacln.p anl_det qqanlmp.p ppacmt.p an_mstr qqanmp.p
Copy Import and Export Specifications
In a multi-domain environment that requires extensive sharing of master data, updates from each domain may need to be propagated to many other domains. Q/LinQ requires similar setup information for each destination domain in each source domain.
To facilitate the creation of similar specifications, you can use Export/Import Spec Copy (36.8.1.4) to copy an export or import specification, updating or creating the destination record. This program can help you streamline the creation of similar
specifications. For example, you can create template records and then make multiple copies of them. This minimizes the number of changes needed to complete setup activities.
This function is especially important in a database that includes multiple domains that need to share master data. To support this synchronization, some setup information for other domains must be maintained in each domain that is going to share data. You can create one source import or export specification for each table to be synchronized and then copy it to the other related domains.
ppacrl.p ans_det qqansmp.p ppcpmt.p cp_mstr qqcpmp.p ppplmt.p pl_mstr qqplmp.p pppcmt.p pc_mstr qqpcmp.p pppimpt.p pi_mstr qqpimp.p
pid_det qqpidmp.p ppptmt.p pt_mstr qqptmp.p pppummt.p um_mstr qqummp.p ppvpmt.p vp_mstr qqvpmp.p rwdpmt.p dpt_mstr qqdptmp.p rwromt.p ro_det qqromp.p rwwcmt.p wc_mstr qqwcmp.p
Destination Procedure Supported Tables Mapping Procedure Name
You must first create the source specifications using Export Specification Maintenance and Import Specification Maintenance.
You can select a specification from any domain as the source of the copy. The target specification is created in the user’s current working domain. In a multiple-database environment, the source domain can exist in another database. The system automatically switches to that domain to find the source record.
If the destination specification exists, the system displays a warning and prompts you to continue. You can overwrite the existing record with values from the source specification.
Fig. 4.23
Import/Export Specification Copy (36.8.1.4)
Choose either Import or Export to indicate the type of specification record to be copied.
Domain. Enter the code identifying the domain associated with the source record to be copied.
You can choose any domain in this database or a connected, remote database. The destination domain defaults to your current working domain and cannot be changed.
Application ID. Enter the ID of the application associated with the source specification to be copied.
This can be the ID of an application registered in Register External Application or the Q/LinQ system ID of a domain as specified in Q/LinQ Control. If you are copying an export specification, it can also be a destination list created in Destination List Maintenance.
To. Enter the ID of the application associated with the specification to be created or updated in the destination domain.
Document Standard, Document Type, Document Revision, Trading Partner ID. Enter values in these fields if required to identify the source specification.
To. Enter values for the destination specification if required. These can be the same as or different than the source specification. Viewing Specification Lists
Use Export/Import Specification List (36.8.1.5) to view import or export specifications for a specified document standard, type, and revision combination. You can view records for a specific domain or for all domains. This lets you quickly see the subscription list of senders or receivers associated with a type of document.