2.1.8.2. MW and eDocuments status map

Transaction:

/EDGE/SII_ CU_012

In this transaction, the error code that the Middleware returns after communication with the AEAT (send) is parameterized. There is a file indicating the relationship between the Middleware response code and the process step on the one hand for communication with PI and on the other hand with FUSE.
When there is communication with the product b+ SII of PI this parameterization is as follows:

Code	Meaning	Relationship with eDocument step
400	Error	ERROR_MW
600	In processing
1002	OK

Field	Meaning
Code	Code that returns the Middleware the shipment
Process Step	Process step that we assign to our eDocuments after receiving the code received after the communication

When the PI returns us an error (400) we set as process step ERROR_MW, this implies a change of the status of the batch of "in process", state that had after making the shipment, to "Technical error".
For communication by FUSE we have the following answers:

Code	Meaning	Relationship with eDocument step
4201	The type of operation does not exist	ERROR_MW
4202	Validation error, wrong password	ERROR_MW
4203	The relationship of tenant and grouping is incorrect for this user	ERROR_MW
4204	Batch fields are required	ERROR_MW
4205	Username does not exist	ERROR_MW
4206	You must provide the authentication data (user/password)	ERROR_MW
4210	Unexpected error	ERROR_MW
4211	Wrong Certificate Key	ERROR_MW
4212	Data input and output error	ERROR_MW
4213	Certificate error	ERROR_MW
4214	Wrong Certificate Algorithm	ERROR_MW
4215	Error creating KeyStore	ERROR_MW
4216	KeyStore of KeyManagers have failed	ERROR_MW
4217	Unable to extract certificate from KeyStore	ERROR_MW
4218	Can not find CACerts on server	ERROR_MW
4219	Mapping error when parsing the data of Invoices, Batch or Answers	MAP_ERROR
4220	General error	ERROR_MW
4999	TIME_OUT	ERROR_MW