Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Revisions: Issue #41978 All Revisions ] Back to Issue ]
Summary 0041978: Import Entry data types without sequence should be sumbitted in last place
Revision 2019-10-10 10:53 by alostale
Description When Import Entry Manager submits new entries to be processed they are grouped by their type of data, these types of data are sorted among them based on their reference list's sequence number.

When they don't have any sequence number defined, 50 is arbitrarily taken.

As there are types with a sequence bigger than 50, they are place in between.

Note there are types defined in standard retail pack without sequence number:

          value          | seqno 
-------------------------+-------
 BusinessPartner         |    10
 BusinessPartnerLocation |    20
 Order                   |    30
 FIN_Finacc_Transaction  |    40
 OBPOS_App_Cashup        |    60
 OBMOBC_ServerMessage    |    70
 OBPOS_RejectQuotation   |    80
 OBPOS_VoidLayaway       |    90
 OBPOS_IsOrderCancelled  |      
 OBPOS_CancelLayaway     |      
 OBMOBC_TerminalLog      |      
 VariantChDescUpdate     |      
 OBMOBC_SynchronizedData |      
 OBPOS_ExternalOrder     |      
(14 rows)
Revision 2019-10-10 10:43 by alostale
Description When Import Entry Manager submits new entries to be processed they are grouped by their type of data, these types of data are sorted among them based on their reference list's sequence number.

When they don't have any sequence number defined, 50 is arbitrarily taken.

As there are types with a sequence bigger than 50, they are place in between.


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker