E1: 03B: P03B602 (Draft Entry) Creates Inconstant EDTN And EDLN In Interoperability Tables (F03B13Z2-F03B13 Interoperability Table and F03B14Z2- F03B14 Interoperability Table) For Multiple Payments (Doc ID 3055015.1)

Last updated on OCTOBER 25, 2024

Applies to:

Symptoms

When enabling the outbound interoperability process there is inconsistent numbering for EDTN (Transaction Number) and EDLN (Line Number) fields in F03B14Z2 and F03B13Z2 tables. This is happening when using P03B602 and entering multiple transactions per batch


The issue can be reproduced with the following steps:
1. Enter JDEREC in the POs of P03B0191 Interoperability with Transaction Type.
2. Create the Interoperability record on P47002 with the same Transaction Type put on P03B0191 processing Option.
3. Setup P0047 (Data Export Controls) with Order Type populated (R1 for example).
4. Run R00460 (Interoperability Generic Outbound Subsystem UBE) with default data selections.
5. Create 3 Drafts for the same batch in P03B602.
6. Post the draft batch created above.

Please review the data in F03B13Z2 and F03B14Z2 before and after posting. The EDTN and EDLN numbers in the F03B14Z2 and F03B13Z2 tables are inconsistent.
Line Number in both F03B13Z2 and F03B14Z2 should be consistent (either consecutive or 1 for each unique Transaction Number)

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.