IBM Support

PI86890: ST CONTROL NUMBER IS INCORRECTLY BEING GENERATED BY THE ENVELOPEDATA INSTEAD OF THE MAP GENERATING IT.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When skipping the generation of transaction header/trailer
    segments in the X12/EDIFACT enveloping services, the transaction
     control number values written to process data and correlations
    are still coming from values in the envelope. For X12, the
    transaction count correlation value is incorrect if exhaust
    input is turned on and the map generates more than one
    transaction.
    

Local fix

  • ITXARTC - RTC00061168
    MG / MG
    Circumvention: None
    

Problem summary

  • Users Affected:
    Customers using custom control numbers
    written by maps during enveloping.
    Problem Description: RTC#61168: When an X12 enveloping
    translation maps generates the control numbers to be used for
    creating the interchange, those control numbers are not
    recognized by the service for constructing the interchange and
    for reporting the correlations.
    When skipping the generation of transaction header/trailer
    segments in the X12/EDIFACT enveloping services, the
    transaction control number values written to process data and
    correlations are still coming from values in the envelope. For
    X12, the transaction count correlation value is incorrect if
    exhaust input is turned on, and the map generates more than one
    transaction.
    Platforms Affected: All
    

Problem conclusion

  • Problem Conclusion:
    When the map generates the transaction control numbers (i.e.
    skip build transaction segments is YES in the envelope), then
    have the X12 enveloping service find the transaction control
    numbers written for each document in Process Data and determine
    the first/last control number for the interchange. Write the
    transaction control number correlations based on the values
    generated by the map.
    Documentation note: The map needs to use the element name
    "MapTransactionControlNumber" when writing control numbers to
    Process Data.
    Applies to:
    SPE.COMMON.9.0.0.6 and SPE.COMMON.9.0.0.7
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI86890

  • Reported component name

    ITX ADV

  • Reported component ID

    5724Q2301

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-09-06

  • Closed date

    2018-02-07

  • Last modified date

    2018-02-09

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Modules/Macros

  • CNTRLNUM
    

Fix information

  • Fixed component name

    ITX ADV

  • Fixed component ID

    5724Q2301

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDF7K","label":"IBM Transformation Extender Advanced"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
15 May 2022