Transformation
Transformation Definition Maint (35.15.17)
Transformation
Name for this transformation definition.
Direction
Direction of the documents to be transformed using this map.
Exchange File, Ver
Name and version of the exchange file definition used in this transformation.
Application, Ver
Name and version of the application document definition used in this transformation.
Implementation, Ver
Implementation definition and version used in this transformation.
Can Run
Yes = makes this transformation map completely operational.
Important: During testing, set this field to No. The system then runs the entire transformation process, but backs the data out of the application repository instead of storing it. Identify mapping problems and correct them before changing this field to Yes.
Debug Level
Enter a value between 0 and 9.
• Level of detail reported in the activity file created when this transformation is run
• Lower levels provide less detail, with zero providing none
• It produces a file in your current home directory and appends sessions in file names <MMDDYYYY.DBG>
Note: You can set this to 9 during testing to get a complete record of what happens during transformation processing.
Warning Leaving this field set to a high value can produce very large files and lead to disk space problems.
Many to Many
Yes = combine multiple input documents and treat them as one or more documents. Allows the system back out multiple files or create a single output from several inputs
No = the system always maps one input document to one or many output documents
• Depends on how many times the transformation definition indicates a new header should be written
Before displaying the second frame, the system creates variables from the exchange file and the implementation associated with this transformation definition. Only these and user-defined variables can be used during transformation, along with the following automatically assigned variables.
• tp-id | • map-name |
• tp-document-id | • map-exf-vers |
• tp-message-nbr | • map-imp-name |
• tp-func-grp-nbr | • map-imp-vers |
• tp-interchange-nbr | • map-mfg-name |
• tp-document-nbr | • map-mfg-vers |
• tp-doc-dir | • map-exf-name |
• tp-site | • map-many-to-many |
• tp-address | • map-debug-level |
• tp-token-val-list | • map-can-run |
• mfg/pro-site | • current-exf-seq |
• mfg/pro-address | • current-mfg-seq |
| • conditional-rec-flushed |
The trading partner variables correspond to tokens. The system uses MFG/PRO-SITE and MFG/PRO-ADDRESS to determine the customer address and the site code automatically, based on the cross-reference defined in Trading Partner Maintenance (35.13.7). You can also assign these values as an event that takes place during transformation. Other variables contain information associated with the transformation definition.
Transformation Definition Maint: Events Frame
In the Event Qualifiers frame, begin identifying a new event by specifying a combination of:
• Event qualifier
• Event
• Record name
• Action sequence
Ev Qual
An event qualifier. The current version of eCommerce uses only the Each option.
Event
Type of event.
• Loop-Entry
• Record-Entry
• Field-Entry
• Loop-Exit
• Record-Exit
• Field-Exit
Record Name
Name of the record that has the event occurring.
Action Seq
A number to represent the sequence in which this event occurs. When setting up event qualifiers, consider using increments of 10 so that intermediate sequence numbers can be inserted later.
Type
Type of action to be performed.
Field Level:
• Equate: Set the target equal to the source
• If: Conditional logic based on source and source qualifier
• The If statement must return a value of True or Yes
• Allows the use of Else and Endif
• Endif: End of an If statement
• Does not require a source or target
• Else: Logical branch between If and Endif statements
• Does not require a source or target
Record Level:
• Read: Read the target record fields into memory
• Can be used only with an input record
• Clear: Remove the target record fields from memory
• Write: Write the target record to the database
• You can only write an output record
• Must write a header record before another record can be written
• Write can be used optionally with the QAD-provided check-hash function, which determines the header for which the detail will be written
• New: Logical place holder for creating outbound transactions
• Loop: Loop through the records already read into memory
• LoopEnd: End a loop
• Does not require a source or target
Qual (target)
Form of data to be specified as the target for this event:
• I: Input data
• O: Output data
• V: Variable
Target
• Inbound record or field
• Outbound record or field
• Variable that is the target of the action specified in Type
Qual (source)
Form of data to be specified as the source for this event:
• I: Input data
• O: Output data
• V: Variable
• C: Constant
• F: Function
Note: If you specify a function and enter its name in Source, another frame lets you modify it as needed for this specific instance. You can also define your own functions with eCommerce Function Maintenance (35.15.21). Use eCommerce Function Copy/Delete (35.17.2) to copy an existing function before modifying it as required.
Source
• Inbound record or field based on qualifier
• Outbound record or field based on qualifier
• Variable
• Constant
• Function that is the source of the action specified in Type
• Modify the qualifiers and parameters as needed for this specific instance
Qual
A code indicating the structure of the data passed in this parameter.
• I: Input data
• O: Output data
• V: Variable
• C: Constant
Parameter
• Name of the input, output, or variable
• If Qual is C, you can enter a constant
• If a value entered is not already defined, the system prompts to define the data type:
• AN: Alphanumeric
• D: Date
• I: Integer
• L: Logical
• R: Real number
