Refer to documentation Implementation
Creation of a rule specifying the input store, then a table to key in the stores to be chained.
Presentation
To create a store chaining, a code that identifies a chaining in a unique manner is attributed to it.
If the chaining is of the « Splitting » type, the priority store so with all the stores of the chaining should be splitting stores.
The splitting type of store is used exclusively on the Merging of Flows functionality
The store is then the priority store of the chaining rule.
Facultative keying in of 1 or several stores. These are examines when there is a failure in the addressing on the principal store.
Close
Fields
The following fields are present on this tab :
Block number 1
| Code of the store sequence. The store sequence defines a priority input store to which stores can be linked if the addressing to said priority input store turns out to be impossible. |
|   |
|   |
| All the stores of the chaining must be allocation stores. |
| Code of the store from which chainings need to be performed in case of a downgrade in the search on input. This code is controlled in the store table. |
Grid Chaining of stores
| Chaining store controlled in the store table. |
Close
In addition to the generic error messages, the following messages can appear during the entry :
Field error, Priority store
The keying in of priority store code is mandatory.
Field error, Priority store
The store should be of the type Splitting if the option « splitting store » is ticked. In the contrary it should be of the type « Principal » or « Mono-address ».
Field error, Store
The keying in of store code is mandatory.
Field error, Store
The chaining of the store should be composed only of stores of the type Splitting if the option « splitting store » is ticked. In the contrary it should be composed of stores of the type « Principal » or « Mono-address ».