Processing-Context-In: Definition Tab

What the Definition tab shows

Defining Processing parameters:

Defining Production parameters:

About the Definition tab

Use this tab to set the following:

  • Properties of the Input-Events recognized by this Processing-Context-In
  • Operating options
  • Processing properties associated with all the Output-Events generated during the session

What the Definition tab shows

The Definition tab is divided into three areas:

  • Definition categories
  • Dynamic pane displaying tabs for the selected category
  • Tree structure of Business-Documents associated with the Processing-Context-In object
    • input Business-Documents
    • output Business-Documents

About the right pane

The right pane comprises two separate drop-down lists, the upper list for existing Input Business-Documents and the lower list for applicable output Business-Documents. When you select a Business-Document, Composer displays the tree structure of its Leaf Elements immediately underneath the relevant drop-down list.

The Processing-Context-In object is comprised of a set of attributes whose values are set in either of the following methods:

  • You type in the values explicitly.
  • The values are provided dynamically in the segments of the Output-Event or Input-Event. With this method you must define the position/length information in the segment itself. To do this, select the Business-Document field that contains the information required when you run the session and then Cut/Paste it from the Business-Document tree structure to the selection zone of the given attribute. You can use specific Business-Document fields as follows:
    • Use fields from the Input Business-Document to complete the Events and Functions tabs.
    • Use fields from the Output Business-Document to complete the Output-Events tab.

About the left pane

The left pane comprises the following category elements that determine the tabs displayed in the middle pane:

  • Processing: the processing options to apply
  • Production: provides information on the session (checks, errors, exits)

Defining Processing parameters

Click the Processing node in the left pane to display the following tabs in the middle pane:

You can identify each field in one of two ways:

  • By Leaf Element
  • Use this method if the field is defined in the Business-Document leaf element being processed. The definition is set by the source application or the Input-Event restructuring exit.
  • Select the In Leaf radio button to activate the field and then drag-and-drop a Business-Document Leaf Element from the right pane.
  • By value
  • Use this method if the identifier has the same value throughout the session.
  • Select the Value radio button to activate the text box and then enter the value, or select it from the drop-down list of relevant objects where available.

Completing the Events tab

Use the Events tab to set the properties of the Input-Events recognized by this Processing-Context-In.

Note   All the Leaf Elements that you use here that are defined By Leaf Element must be taken from input Business-Documents only.

Input-Event name

Field Description

Input-Event name

Select one of the following options to indicate where to find the Input-Event name:

  • Value:Select the Input-Event name from the drop-down list.
  • In Leaf: Select the In Leaf radio button and drag-and-drop an input Business-Document Leaf Element into the field.

The associated field must be alphanumeric, with a length between 1 and 25 characters.

Input-Event release

Field Description

Input-Event version

Specify where to find the Input-Event release code to indicate which version of the Input-Event the Processing-Context-In can use:

  • Value: Enter either of the following depending on the method you use to identify the version of the Input-Event:
  • a number between 1 - 999
  • a date between 01/01/1900 et 31/12/2099
  • In Leaf: From the Business-Document tree structure in the right pane, drag-and-drop the field which stores the Input-Event version.

Identified by a number instead of a date

Rule Engine provides several methods you can use to identify the version of an Input-Event:

  • by validity date
  • by directly specifying the version number

By default AccountingIntegrator Enabler identifies an Input-Event by its validity dates. The date you enter enables the system to determine which validity period is activated and therefore which Input-Event version is valid for the specified date.  

Select this check box if you do not want to use the default identification method, but want to identify the Input-Event directly by its version number instead.

The data type required depends on the  method you select to identify the Input-Event version:

If the version is identified by Number, the corresponding field must be Numeric or Packed, with a length of three characters.

If the version is identified by Date, the corresponding field must be one of the following:

  • Date, Numeric or Packed (length 6 to 8 characters)
  • Alphanumeric (length 10 characters which corresponds to the DD/MM/YYYY date format.)
    This length and format is the same as in the Input-Event version field.)

Segment type name

Field Description

Segment type name

Specify where to find the Segment type name:

  • Value: Select a segment type name from the drop-down list.
  • In Leaf: Drag-and-drop a Leaf Element from the right pane.
    The corresponding field must be alphanumeric of 1 to 25 characters in length.

Instance code

An Instance code is mandatory for multi-segment Input-Event processing. This information enables AccountingIntegrator Enabler to group segments which have the same instance code into a single instance.

Field Description

Instance code

Select this check box to activate the radio buttons to indicate where to find the Instance code:

  • Value: Enter an Instance code in the text box.
  • In Leaf: To retrieve the Instance code from an existing Business-Document, drag-and-drop a Leaf Element from an input or output Business-Document in the right pane.

    The corresponding field must be one of the following:
  • alphanumeric of length 1 to 34 characters
  • numeric of length 1 to 28 characters

Note: If AccountingIntegrator Enabler evaluates the instance code and finds it only contains blanks spaces, AccountingIntegrator Enabler considers the segment as a mono-segment Input-Event.

Maximum number of segments by event

The limit in Composer is 999. However you can set a higher technical limit in  Rule Engine.

If you set the limit to:

  • 0: AccountingIntegrator Enabler considers there is no explicit maximum number of segments.
  • 1: This implies that the Input-Events are independent. If the system rejects a segment this does not affect the other segments in the same instance.

If the limit you set is exceeded during the transformation process, that is, the number of segments in the Input-Event being processed is more than your specified limit, AccountingIntegrator Enabler writes a non-blocking message in the processing report:

"Warning: The number of segments in Input-Event <XX> exceeds the limit <LIMIT> you set."

Date of application for rules

Field Description

Date of application for rules (DAR)

Check one of the following options to indicate the date on which Rules are applied:

  • Operation date: Sets the value of the DAR to the operation date set in the implementation script.
  • Rule Engine Reference Guide
  • In Leaf: The corresponding field must be one of the following:
  • Numeric or Packed (6 to 8 characters long)
  • Date (10 characters long, which corresponds to the DD/MM/YYYY date format.)
    This length and format is the same as in the Input-Event version field.

Completing the Functions tab

The Functions tab provides operating options to the engine (Rule Engine). Each element has a check box which you select to activate the associated functions. If you activate a function, you must set the parameters for it.

You can only drag-and-drop Input Business-Documents into the fields in this tab.

The available check boxes are:

  • Aggregation
  • Balancing check
  • Accounting processing
  • Group management
  • Phase recycling
  • Audit

Aggregation

Check it to implement Input-Event and Output-Event aggregation functions in the session.

Balancing check

Check it to implement balancing checks in the session on the Output-Events generated from the highlighted Input-Events.

Use the radio buttons to define when to run the balancing check on the Output-Event segments:

  • Always check
  • In Leaf: Drag-and-drop the input Business-Document Leaf Element which stores the balancing check code.

This code must be set to 1 if you want the system to include the Output-Events from the given Input-Event in the balance check.

Accounting processing

Check it to activate the Reversal processing.

Use reversal processing to reverse the direction of accounting type Output-Events generated in error by some Input-Events. This only concerns Output-Events routed to Processing-Context-Outs where Accounting Checks are activated.

Select one of the following options:

  • Always reverse automatically. Reversal operation is made according to the parameter settings specified in the Processing-Context-Out.
  • In Leaf: Drag-and-drop the Business-Document Leaf Element which stores the Reversal Code. The Reversal Code must be set to "2" for the Input-Events to be "reversed".

Group management

Check it to implement Input-Event management by group.

You can group Input-Events as part of a logical set. To ensure that the system receives and treats all these product Input-Events, use this option to set group management to reject the entire group of Input-Events if one Input-Event in that group fails.

When the system rejects the group of Input-Events, it displays an error message stating:

  • For the specific Input-Event rejected, the defective Business-Document that caused the error.
  • For the other Input-Events in the same group, that the failure is due to a defective Input-Event within the defined group.

Set the group number using either of the following:

  • Value: Enter a fixed value for the group number.
  • For example, if you enter the value 1 in this field, all Input-Events linked to this Processing-Context-In will be set to group number 1. The system then rejects all Input-Events in group 1 if any one of them fails.
  • In Leaf: Drag-and-drop the Business-Document Leaf Element which stores the group number.
  • The system checks this Business-Document field to see to which group the Input-Event belongs.

The maximum length of the group number field depends on the data type:

  • Alphanumeric: 34 characters
  • Numeric: 28 characters
Note   If AccountingIntegrator Enabler evaluates the group number and finds it only contains blanks spaces, AccountingIntegrator Enabler considers the Input-Event as not part of the group.

Phase recycling

Authorize the processing of Input-Events in error, in a given Phase and in a given session. Use the radio buttons to define the Phase code to be processed:

  • Value: Select a Phase code associated with the Input-Event from the drop-down list
  • In Leaf: Drag-and-drop the Business-Document Leaf Element which stores the Phase code.

Audit

Check it to implement Input-Event auditing.

In the format of every input segment to be audited, make sure that there is a technical field into which AccountingIntegrator Enabler can, if necessary, write the Stamping Code. When you select this Audit option, AccountingIntegrator Enabler automatically activates this field.

  1. Use the radio buttons to select the audit trace stamp method. The stamp method depends on the data type of the selected Stamping Code field:
  2. Timestamp writes the date and time the Audit-Rules was executed on the Input-Event. The stamp identifier is alphanumeric, 25 characters long and comprises:
  3. Stamp code [5A]+operating date [YYYYMMDD]+stamp time [HHMMSS] +identifying letter [1A]+stamping counter [N5]
    • Serial numeric stamping writes a sequential number which increments with each audited Input-Event. The stamp identifier is alphanumeric, 2-19 characters long and comprises:
    • Identifying letter [1A]+stamping counter[N1to N18]
    • Serial packed stamping writes a sequential number using the Packed Data Type. The stamp identifier is alphanumeric, 2-19 characters long and comprises:
    • Identifying letter [1A]+stamping counter[P1 to P18]
  4. Select the Event stamping identifier update check box for AccountingIntegrator Enabler to mark each segment with a unique stamp identifier. Otherwise, AccountingIntegrator Enabler will consider the field contents as a stamp identifier specified beforehand and will therefore not check that the identifier is in fact unique.
  5. From the input Business-Document leaf list, drag-and-drop the field containing the Event stamping identifier update code.
  6. Select the Audit Multi-session option to keep a link between Output-Events created in one session and used as Input-Events in another session. This option is enabled only if the Audit check box is selected.
    • If this option is not selected (default), stamping radio buttons and Origin event stamping field are disabled.
    • If this option is selected, the Origin event stamping field is mandatory but cannot be edited. You can only drag and drop a leaf element from the input Business-Document.

Completing the Output-Events tab

Use the Output-Events tab to configure processing properties associated with all the Output-Events generated during the session.

Note   There is no direct link between the Processing-Context-In and the Processing-Context-Out objects that you reference in this table.

In the field Processing-Context-Out code, specify where to find the code for the Processing-Context-Out object to which AccountingIntegrator Enabler sends the Output-Event:

  • Output-Event: This option signifies that the Processing-Context-Out is contained within an Output-Event field.To retrieve the code that identifies the Processing-Context-Out, drag-and-drop the relevant field from the output Business-Document tree structure in the right pane.
  • Value: From the drop-down list, select a Processing-Context-Out code value.
  • Business-Document code: The Processing-Context-Outcode is the first character in the Business-Document name.
  • Exit: If the Processing-Context-Outcode is provided by an external program, use this option to activate the use of Exits in this Processing-Context-In. Rule Engine automatically links the appropriate $SEARCH function.

For more information, refer to the AccountingIntegrator Exits and External Calls guide.

If options is activated on the Functions tab, you must indicate where to find the codes to identify each of the Rules applicable to Output-Events:

Field Description

Aggregation-Rule identification

Balancing-Rule identification

Identify the Aggregation-Rule or Balancing-Rule by one of the following methods:

  • Processing-Context-Out: Rule name identifier is set in the Processing-Context-Out
  • Output-Event segment: Rule name identifier is in the Output-Event segment
Audit-Rule identification

Identify the Audit-Rule by one of the following methods:

  • Processing-Context-Out: Rule name identifier is set in the Processing-Context-Out
  • Output-Event segment: Rule name identifier is in the Output-Event segment
  • Business-Document: The name of the Audit-Rule corresponds to the name of the Output-Business-Document

Completing the Script configuration tab

Use the Script configuration tab to configure the behavior of the Rule Engine session, associated to the context-in.

Note   There is no direct link between the Processing-Context-In and the Processing-Context-Out objects that you reference in this table.
Field Description
Step

Defines the different steps to be activated in the Rule Engine session.

Possible values: E, T, S, ETS, ET, TS

Default value: ETS

Refer to "Steps in a transformation session and sys.dat file" in the AccountingIntegrator Enabler User Guide for more information about the possible steps.

Decimal division

Defines the behavior of Rule Engine in case of decimal division

Possible values: Yes, No

Default value: No

Codification

Defines the way to code the sign for signed and packed data for Unix platforms.

Possible values: ASCII, EBCDIC

Default value: EBCDIC

Input-Event sort

Enables the sort action for the input events file.

Possible values: Yes, No

Default value: No

If this option is enabled, it includes the following parameters:

Memory_Sort

  • Possible values: Integer, no limit
  • Default value: 5000
  • Must accept only numeric values

Length_Average_Isegt

  • Possible values: 1 to 4000
  • Default value: 100
  • Must accept only numeric values, size - 4 characters

Length_Average_Osegt

  • Possible values: 1 to 4000
  • Default value: 100
  • Must accept only numeric values, size - 4 characters
Note   If I_Sort_Ievent is not active, Memory_Sort, Length_Average_Isegt, Length_Average_Osegt are disabled.
Audit of rejects and anomalies

Enables the generation of audit traces for the rejected events and in transformation anomaly.

Possible values: Yes, No

Default value: No

Dispatch Process ContextOut in step P

Enables the computation of the output events dispatching to context out in the P step.

Possible values: Yes, No

Default value: No

Output Event Aggregation

Not a configuration parameter, this element is used to group two parameters because they cannot be enabled at the same time.

By default, it is not checked, it depends on the Aggregation field from the Functions tab. If the Aggregation is not active, the field Output Event Aggregation is not enabled.

The two parameters included are:

O_Aggregation_Osegt – Enables the output events aggregation.

  • Possible values: Yes, No
  • Default value: No

P_Aggregation_OSegt_Group – Enables the output events aggregation with the group code as implicit criteria.

  • Possible values: Yes, No
  • Default value: No
Partial Aggregation Partial aggregation for Input Event

Enables the partial aggregation. For example, for an Input Event aggregation, it generates intermediary results when the aggregated value length is bigger than the property physical length.

Aggregation_Part_IEvent

Possible values: Yes, No

Default value: No

Partial aggregation for Output Event

Enables the partial aggregation. For example, for an Output Event aggregation, it generates intermediary results when the aggregated value length is bigger than the property physical length.

Aggregation_Part_OSegt

Possible values: Yes, No

Default value: No

Defining Production parameters

Click the Production node in the left pane to display the following tabs in the middle pane:

Completing the Controls and Optimization tab

Use the Controls and Optimization tab to set the session operating options.

Check box If selected If unselected

Check numeric order

Sets a check on mapping results in the numeric fields of the modified Output-Event or segments. The system checks whether the field contents are Packed, Numeric or Signed.

The Input-Event is in error if the check fails.

It is recommended that you always activate this option. select the Check numeric order field since it is valid for every Input-Event that uses this Processing-Context-In.
To change this setting for a specific Input-Event, use an Enrichment-Rule to modify the contents of this field.

AccountingIntegrator Enabler does not perform any check and does not reject an Input-Event with non-numeric values in Integer fields.

Check Table entries existence in Table

The processed Input-Event is in error if a Table key search is unsuccessful.

Input-Event processing is considered to be correct, irrespective of the result of the Table search.

Check rule existence

At session startup, the existence of all the defined rules is checked. If a rule is missing, the session is shut down.

The processed Input-Event is in error when a non-existent rule is applied.

Check generation of at least one Output-Event per event

If an Input-Event is transformed and no Output-Event is generated, the Input-Event is rejected.

An Input-Event transformation without a generated Output-Event is considered to be correct.

Check generation of at least one Output-Event per transformation rule

If a Transformation-Rule is executed and no Output-Event is produced, the Input-Event fails.

If a Transformation-Rule is executed and no Output-Event is produced, the transformation is considered to be successful.

Optimize Output-Event length

The Output-Event is written to the length of its structure.

The Output-Event is written to 4000 characters (with added spaces).

Delete empty fields to right of business event *

The length of the Output-Event is reduced if the final fields of the structure are mapped with spaces.

The Output-Event is written to the complete length of the structure.

Route Input-Events

The Input-Events successfully processed in the session are routed to AccountingIntegrator Enabler output files.

 

*This option is not recommended for an Oracle type session, when null value management is used.

Completing the Errors tab

Use the Errors tab to configure the session shutdown options, depending on the errors detected. AccountingIntegrator Enabler stops processing the Rule and continues with the other Rules within the same Phase.

Field Function

Maximum Error Detection

If you select this check box, the transformation continues in a Transformation-Phase after an error has been detected in a rule.

Otherwise, the rule execution process passes to the next Phase when an error is detected in a Transformation-Phase.

Maximum percentage of rejected events for session shutdown

 

If you enter:

  • zero, the session is considered to be valid, irrespective of the percentage of rejected Input-Events.
  • a value other than zero, the whole session is executed, but declared invalid, if more than the specified percentage of Input-Events are rejected.

Number of rejected events for session shutdown

If you enter:

  • zero, the transformation is completed, irrespective of the number of rejected Input-Events.
  • a value other than zero, the session is shut down when the specified number of rejected Input-Events is reached.

Number of rejected event groups for session shutdown

If you enter:

  • zero, the transformation is completed, irrespective of the number of rejected Input-Event groups.
  • a value other than zero, the session is shut down when the specified number of rejected Input-Event groups is reached.

Completing the Exits tab

Use the Exits tab to define the type of Exit you want to activate in the session associated with the Processing-Context-In. For more information, refer to the AccountingIntegrator Exits and External Calls guide.

Select the check box to activate the associated exit, then use the radio buttons to specify one of following exit types:

  • Exit written in C (C option)
  • Exit written in COBOL (COBOL option)
  • Exit written in COBOL, compatible with the same exit level in Release 1.5.3.2. (RDJ53 option)
Check box When selected, use the radio buttons to select the required exit When unselected

Event check and enrichment before Transformation-Phase exit type

  • C: activates EXIEEN in plgc.c
  • COBOL: activates EXIEEN.CBL
  • RDJ53: activates ITR506.CBL

The EXIEEN (or equivalent) exit is not activated.

Event check and enrichment for application exit type

  • C: activates EXIERG in plgc.c
  • COBOL: activates EXIERG.CBL
  • RDJ53: activates ITR506.CBL

The EXIERG (or equivalent) exit is not activated.

Output-Event identification and check exit type

  • C: activates EXIEME in plgc.c
  • COBOL: activates EXIEME.CBL
  • RDJ53: activates ITR506.CBL

The EXIEME (or equivalent) exit is not activated.

Restructuring exit of Input Event during step E
  • C: activates EXIRST in plgc.c
  • COBOL: activates EXIRST.CBL
The EXIRST exit is not activated
Restructuring exit of Output Event during step S C: activates EXIRME in plgc.c The EXIRME is not activated
Aggregation exit of Input Event during step E
  • C: activates EXAEEN in plgc.c
  • RDJ53: ITR025.CBL
The matching exit is not activated
Aggregation exit of Output Event during step S
  • C: EXAEME
  • RDJ53: ITR615.CBL

 

Aggregation exit of Output Event by group during step T
  • C: EXAEME
  • RDJ53: ITR615.CBL
 

Related Links