Unique internal ID of a record within the table. The INR is a text field, which is created by retrieving the next valid entry from the counter of this table. The field INR is used to enable links from other tables to this table.

For contractdata the INR also links the two tables xxD and xxT as associated entries hold the same INR.

This field holds the INR of the allNETT contract to which the allNETT transaction belongs

Type of contract the ANA entry refers to. This is the table the contract is stored in.

INR of the contract within the table, defined in OBJTYP.

INR of the related TRN record which created the ANB.

Identifies an allNETT step being an request of an amendment.

This field holds the INR of the SMH record that holds the allNETT message

allNETT message direction (from allNETT perspective)

key for loadanaanb in srvani ISS = Issuance AMD = Amendment PAY = Payment APA = Actual Payment ACP = Acceptance AAC = Actual Acceptance POA = Payment of Acceptance MSC = Miscellaneous TFR = Transfer TAM = Transfer Amendment BKF = Book Off

Additional subtype for allNETT messages to further specify the type of message (e.g. reason of a free format message).

This field holds the external key of the owning entity to identify the logical owner of this entry.

This field is filled automatically during insert and is used as filter when accessing the database. Without special implementation only entries of the currently active entity are visible to the user.

If an incoming allNETT message is referring to preceeding transactions as i.e. for document sets, then this INR pointers to the ANB record of the preceeding transaction which was created as outgoing message from DOKA-NG.

key for loadanaanb in srvani

Number that uniquely identifies the POA within the deal.

related allNETT step_no

Currecntly used to send the related AMD Step_no in D2A message MSC from LETRAM.

related allNETT step

Currecntly used to send the related AMD Step in D2A message MSC from LETRAM.

Might be enhanced to other steptyp in the future.

If set, the ANB Record is linked to a 2nd ANA record for an existing DOKA Contract.

Used in Sector Guarantees where Applicant AND Beneficiary are both allNETT customers of the Bank.

In this case two ANA records pointing to the same record (via OBJINR / OBJTYP) exists. With flag being empty is the ANA Record for the Applicant. With Flag being set is the ANA Record for the Beneficiary.

Flag to identify if for an incoming allNETT message the Status 90 (DOKA-NG processing transaction is finally released) has been send to allNETT.

allNETT misc_type in case message is a miscellaneous message.

This is the number of the received amendment in case of an AME / RAM transaction is processed.

Needed in case of a rejection of an detrimenral amendment for LI and GI in order to find the relevant pntstep and related step.

Normally ANTINCDELTYP and ANTDELTYP are equal.

But in case a Shipping Guarantee is requested for a not yet received import collection, the ANTDELTYP is 03 and ANTINCDELTYP is 22.

In case the D2A allNETT message is created from a subcontract (e.g. documentset) this field contains the reference of the Sub contract. In all other case the reference of the main deal.

allNETT customer reference for shipping guarantees deals.

Send in D2A messages and should be included in all D2A message linked to that transaction including status messages.

incoming message had BOTPOP_Flag set to true. Can be used in customer overlay to route message to BOTPO instead of BOTDAV

This field holds the version counter used to keep track of the history of an entry of this table. The individual versions are managed by entries in the SLG table.