IBM Support

IT38168: EBICSORDERPROCESSING IS WRITING IN FS, BUT IT SHOULD BE IN DATABASE

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

  • EbicsHttpAdapter gives option to store document (payload) in
    DB,FS SD
    
    But for technical upload orders even after setting adapter to
    DB, the payload of orders like FUL, CCT and XCT are storing it
    in FS.
    

Local fix

Problem summary

  • Problem Description:
    
    
    
    EBICSOrderProcessing is writing in FS, but it should be in
    database
    
    
    
    EbicsHttpAdapter gives option to store document (payload) in
    DB,FS SD
    
    But for technical upload orders even after setting adapter to
    DB, the payload of orders like FUL, CCT and XCT are storing it
    in FS.
    
    
    
    After Fix : For all technical Upload Orders the payload will be
    stored as per the adapter setting.
    
    
    
    Platforms Affected:
    
    All
    
     Users Affected:
    
    All EBICS users
    

Problem conclusion

  • Resolution Summary:
    
    
    
    The documents stored will always use the property set as per
    jdbcService.defaultDocumentStorageType=FS/DB however, the EBICS
    request and payload (streamed document) will be stored as per
    the setting on the adapter.
    
    
    
    Delivered in:
    
    6000305
    
    
    
    All future Fix Packs can be found in the Release Timeline
    Matrix.
    
    
    
    https://www.ibm.com/support/pages/node/6194265
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT38168

  • Reported component name

    STR B2B INTEGRA

  • Reported component ID

    5725D0600

  • Reported release

    603

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    YesSpecatt / New Function / Serviceability /

  •  

    Xsystem

  • Submitted date

    2021-08-27

  • Closed date

    2021-10-05

  • Last modified date

    2021-10-05

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

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

Fix information

  • Fixed component name

    STR B2B INTEGRA

  • Fixed component ID

    5725D0600

Applicable component levels

[{"Line of Business":{"code":"LOB02","label":"AI Applications"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS3JSW","label":"Sterling B2B Integrator"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"603"}]

Document Information

Modified date:
06 October 2021