IOM Response Status Model

Description

Statuses of a response.


Note

For services, that are using this model the statuses must be used prefixed with STATE_.

I.e., for the status INITIAL it will be returned STATE_INITIAL.



Product Version

4.0

Product To Version

Status

New Labels





States

The following table lists all states of Response Status Model with IDs and short descriptions.

StateIDDescription
INITIAL0Response initially stored in the database
NOT_CHECKED999Validation of the response failed. The response has to be checked manually
CHECKED1000Response was checked
DO_ANNOUNCE4001Response is ready to be announced to the order
ANNOUNCED4100Response is successfully announced to the order
DO_PROCESS3001Response is ready to process
PROCESSED6000Response was processed
DO_COMPOSE_RESPONSE4701

An additional response based on this response must be created

COMPOSED_RESPONSE4800Response to the shop was created
DO_RETURN4401Return based on the response is ready be created
RETURNED4500Return based on the response was created
DO_CHECK500Response has been checked/ edited manually and is ready to be processed
DO_CLOSE7901Response process can be closed
IN_EXTERNAL_PROCESSING8900Response is in external processing, because of errors
NOT_CHECKED_DO_APPROVE995Validation of the response failed. The response has to be checked manually
DO_PREPARE_DOCUMENT7001Required objects to prepare documents are ready to be created
PREPARED_DOCUMENT7100Required objects to prepare documents are created and ready to use
WAIT_MERGE10000Response was stopped because of order merge. Status is wait without status transitions
COPIED_FOR_MANUAL_EDIT9999Copy of the message for manual editing is created
WAIT_PENDING11000Response was stopped after creation of new dispatch. Status is wait without status transitions
FAILED9000Processing of response failed
CLOSED8000Processing of response is successfully closed

Model

The following model shows the different states and the possible transitions between the states.

Disclaimer

The information provided in the Knowledge Base may not be applicable to all systems and situations. Intershop Communications will not be liable to any party for any direct or indirect damages resulting from the use of the Customer Support section of the Intershop Corporate Web site, including, without limitation, any lost profits, business interruption, loss of programs or other data on your information handling system.

The Intershop Customer Support website uses only technically necessary cookies. We do not track visitors or have visitors tracked by 3rd parties.

Further information on privacy can be found in the Intershop Privacy Policy and Legal Notice.
Customer Support
Knowledge Base
Product Resources
Tickets