Process documentationArchiving Payment Data Locate this document in the navigation structure

 

You can use this process to archive, delete, and display payment orders and recalls in Payment Engine.

Note Note

All order types, incoming orders, outgoing orders, and letters of advice (advice orders), use the same archiving objects. There are no separate archiving objects for payment items and collectors – they are archived as part of the referenced order.

End of the note.

Prerequisites

You have carried out customizing activities to adapt the archiving processes for Payment Engine to your requirements.

For more information, see Customizing Payment Data Archiving.

Process

Archiving Payment Orders

Payment Engine can process payment orders containing more than 1,000,000 payment items. Because of this huge amount of data, one archiving object instance is not sufficient, as this would lead to runtime errors due to memory overflow. Therefore, two archiving objects are used for payment orders:

  • Order analysis (/PE1/ORD1)

    This archiving object splits large payment orders into smaller technical order objects.

    During the analysis, the residence time and business checks are also executed:

    • Residence time check

      You can configure residence times in the Archiving Engine using transaction AR_CUST.

      You can make more detailed settings on Clearing Area level using transaction AR_HDS. Since archiving object /PE1/ORD1, which performs residence time checks, is assigned to retention policy procedure Hierarchical, the system internally evaluates all customizing settings and checks whether an order can be archived based on its residence time.

      Note Note

      The residence time is calendar independent and can be maintained in days, weeks, months, or years.

      End of the note.

    • Business check

      The system only checks the payment order state and, thus, needs to read no other data. If the check is positive, the system archives the object; if it is negative, it increases the resubmission date by the period defined in the Archiving Engine customizing.

      Archiving is permitted, if one of the following states apply:

      • Inbound processing finished

      • Rejected

      • Processed in Output Manager (OPM)

      • Outbound processing finished

      • Reversed

    If a payment order can be archived, it is written as a single technical order object into table /PE1/DB_ORDER_AR. A database buffer used as a header table for payment order and payment item archiving (/PE1/ORD2).

    If a payment order needs to be split, the system writes multiple technical order objects into table /PE1/DB_ORDER_AR.

    Example Example

    Using archiving object /PE1/ORD1, the system finds a payment order containing 1,000,000 payment items. It splits this payment order into 100 packages of 10,000 items each and writes these packages as technical order objects into table /PE1/DB_ORDER_AR.

    End of the example.

    For more information, see Archiving Payment Orders (Analysis).

  • Order archiving (/PE1/ORD2)

    This archiving object archives the technical order objects.

    Order archiving comprises writing and deleting phases:

    • Write phase

      All order entries in table /PE1/DB_ORDER_AR are written to archive files. No further checks are necessary here (neither residence time nor business checks)

    • Delete phase

      This phase is used to read the written archive file and delete the corresponding database table entries.

      Note Note

      The system does not delete payment items and payment-item dependent tables in this phase.

      For more information, see Deleting Payment Items.

      End of the note.

    For more information, see Archiving Payment Orders (Archiving).

Archiving Recalls

The system uses only one archiving object for recalls, recall archiving (/PE1/RCL).

Recall archiving comprises these phases:

  • Analysis phase

    During the analysis, the system checks the residence time and performs the business checks.

  • Write phase

    All recall entries (in table /PE1/DB_RECALL) are written to archive files.

  • Delete phase

    The system reads the written archive file and deletes the corresponding database table entries.

    Note Note

    The system does not delete payment items and payment-item dependent tables in this phase.

    For more information, see Deleting Payment Items.

    End of the note.

For more information, see Archiving Recalls.

Displaying Payment Orders and Archived Data

You can view payment orders in the archiving application.

For more information, see Displaying Payment Orders.