| Description | Manage Engineering Change Order |
| Name | ManageEngineeringChangeOrderIn |
| Namespace | http://sap.com/xi/A1S/Global |
| Process Component Description | Engineering change processing |
| Process Component Name | EngineeringChangeProcessing |
| Process Component Namespace | http://sap.com/xi/AP/FO/EngineeringChangeOrder/Global |
| Deployment Unit Description | Foundation |
| Endpoint Activation | By Scoping of Process Component | Operations |
| Release Status | Not Released |
An interface to read or create engineering change order data.
The web service interface Manage Engineering Change Order In enables you to connect external applications to your SAP Business ByDesign system and to create and edit engineering change orders in your system. The web service interface Manage Engineering Change Order In is relevant if your company wants to create or read engineering change order data from external applications.
The web service interface Manage Engineering Change Order In offers the operations CREATE_ECO and READ_ECO.
The READ_ECO operation, and an engineering change order must exist in the system.
Action codes represent an instruction to the recipient of the web service request to process transmitted message node elements.
| Action Code | Description |
|---|---|
| 01 | Create; the system returns an error message if the node element already exists. |
| 02 | Update; the system returns an error message if the node element does not exist. |
| 03 | Delete; the system returns an error message if the node element does not exist. |
| 04 | Save; the system creates or changes the node element data. |
| 05 | Remove; the system deletes the node element. If the node element does not exist, the system does not send an error message. |
| 06 | No Action; the system does not change the node element. |
Default action code: 04 (Save).
Note: Action code 04 (Save) creates business documents if the system cannot identify a matching target business document. This applies if no business document ID or UUID is provided by the web service consumer. The web service consumer (external application) is responsible for providing correct business document IDs or UUIDs and to avoid accidental creation of duplicate business documents.
Sample example of web service request that requests to create an engineering change order:
<n0:EngineeringChangeOrderCreateRequest_sync xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <EngineeringChangeOrder> <ID >CREATE_ECO</ID> <TypeCode>5</TypeCode> <Validity> <StartDate>2014-07-24</StartDate> <CancelledIndicator>false</CancelledIndicator> </Validity> </EngineeringChangeOrder> </n0:EngineeringChangeOrderCreateRequest_sync>
Sample example of response for Create operation:
- <n0:EngineeringChangeOrderCreateConfirmation_sync xmlns:n0="http://sap.com/xi/SAPGlobal20/Global" xmlns:prx="urn:sap.com:proxy:ACL:/1SAI/TAS8426815B27B79C4C1188:804"> - <EngineeringChangeOrder> <UUID>00163e07-3d6a-1ee4-84c8-be28b556dfb5</UUID> <ID>CREATE_ECO</ID> </EngineeringChangeOrder> - <Log> <MaximumLogItemSeverityCode>1</MaximumLogItemSeverityCode> - <Item> <TypeID>007(/CSG_RUNTIME/)</TypeID> <SeverityCode>1</SeverityCode> <Note>Create operation was successful</Note> </Item> </Log> </n0:EngineeringChangeOrderCreateConfirmation_sync>
Sample example of web service request that requests to read an engineering change order:
<n0:EngineeringChangeOrderByIDQuery_sync xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <EngineeringChangeOrder> <ID>CREATE_ECO</ID> </EngineeringChangeOrder> </n0:EngineeringChangeOrderByIDQuery_sync>
Sample example of response for Read operation:
<n0:EngineeringChangeOrderByIDResponse_sync xmlns:n0="http://sap.com/xi/SAPGlobal20/Global" xmlns:prx="urn:sap.com:proxy:ACL:/1SAI/TAS206410A5408C3B4CEB90:804"> <EngineeringChangeOrder> <UUID>00163e07-3d6a-1ee4-84c8-b4cbaaa61fac</UUID> <ID>CREATE_ECO</ID> <TypeCode>5</TypeCode> <TypeName>Single-date Order</TypeName> <Status> <LifeCycleStatusCode>1</LifeCycleStatusCode> <LifeCycleStatusName>In Preparation</LifeCycleStatusName> </Status> <SystemAdministrativeData> <CreationDateTime>2014-07-23T08:45:08.533421Z</CreationDateTime> <CreationIdentityUUID>00163e04-f8f7-1ee2-b4be-e5160f59853c</CreationIdentityUUID> <LastChangeDateTime>2014-07-23T08:45:46.771632Z</LastChangeDateTime> <LastChangeIdentityUUID>00163e04-f8f7-1ee2-b4be-e5160f59853c</LastChangeIdentityUUID> </SystemAdministrativeData> <ChangeGroup> <UUID>00163e07-3d6a-1ee4-84c8-b4cbaaa63fac</UUID> <ID>CG0000000001</ID> <MainIndicator>true</MainIndicator> <Status> <ProcessingStatusCode>1</ProcessingStatusCode> <ProcessingStatusName>Not Started</ProcessingStatusName> <EngineeringChangeOrderLifeCycleStatusCode>1</EngineeringChangeOrderLifeCycleStatusCode> <EngineeringChangeOrderLifeCycleStatusName>In Preparation</EngineeringChangeOrderLifeCycleStatusName> </Status> <SystemAdministrativeData> <CreationDateTime>2014-07-23T08:45:08.533421Z</CreationDateTime> <CreationIdentityUUID>00163e04-f8f7-1ee2-b4be-e5160f59853c</CreationIdentityUUID> <LastChangeDateTime>2014-07-23T08:45:08.533421Z</LastChangeDateTime> <LastChangeIdentityUUID>00163e04-f8f7-1ee2-b4be-e5160f59853c</LastChangeIdentityUUID> </SystemAdministrativeData> </ChangeGroup> <Validity> <TechnicalID>00163E073D6A1EE484C8B4CBAAA67FAC</TechnicalID> <StartDate>2014-07-24</StartDate> <MainIndicator>true</MainIndicator> <ActivationDateTime timeZoneCode="UTC" /> <Status> <ReleaseStatusCode>1</ReleaseStatusCode> <ReleaseStatusName>Not Released</ReleaseStatusName> <EngineeringChangeOrderLifeCycleStatusCode>1</EngineeringChangeOrderLifeCycleStatusCode> <EngineeringChangeOrderLifeCycleStatusName>In Preparation</EngineeringChangeOrderLifeCycleStatusName> </Status> <SystemAdministrativeData> <CreationDateTime>2014-07-23T08:45:08.533421Z</CreationDateTime> <CreationIdentityUUID>00163e04-f8f7-1ee2-b4be-e5160f59853c</CreationIdentityUUID> <LastChangeDateTime>2014-07-23T08:45:46.771632Z</LastChangeDateTime> <LastChangeIdentityUUID>00163e04-f8f7-1ee2-b4be-e5160f59853c</LastChangeIdentityUUID> </SystemAdministrativeData> </Validity> <ChangeStateID>20140723084546.7716320</ChangeStateID> </EngineeringChangeOrder> <Log /> </n0:EngineeringChangeOrderByIDResponse_sync>
You can find general information about Web services, their structure and consumption in the Web Services documentation. Please open the Web Services document in a new window.
| Description | Create engineering change order |
| Name | Create |
| Synchronous | yes |
| Release Status | Released |
To create an engineering change order.
The web service interface Manage Engineering Change Order In enables you to connect external applications to your SAP Business ByDesign system and to create and edit engineering change orders in your system. The web service interface Manage Engineering Change Order In is relevant if your company wants to create or read engineering change order data from external applications.
The web service interface Manage Engineering Change Order In offers the operations CREATE_ECO and READ_ECO.
Action codes represent an instruction to the recipient of the web service request to process transmitted message node elements.
| Action Code | Description |
|---|---|
| 01 | Create; the system returns an error message if the node element already exists. |
| 02 | Update; the system returns an error message if the node element does not exist. |
| 03 | Delete; the system returns an error message if the node element does not exist. |
| 04 | Save; the system creates or changes the node element data. |
| 05 | Remove; the system deletes the node element. If the node element does not exist, the system does not send an error message. |
| 06 | No Action; the system does not change the node element. |
Default action code: 04 (Save).
Note: Action code 04 (Save) creates business documents if the system cannot identify a matching target business document. This applies if no business document ID or UUID is provided by the web service consumer. The web service consumer (external application) is responsible for providing correct business document IDs or UUIDs and to avoid accidental creation of duplicate business documents.
| Description | Read engineering change order |
| Name | Read |
| Synchronous | yes |
| Release Status | Released |
To read the data of an engineering change order.
The web service interface Manage Engineering Change Order In enables you to connect external applications to your SAP Business ByDesign system and to create and edit engineering change orders in your system. The web service interface Manage Engineering Change Order In is relevant if your company wants to create or read engineering change order data from external applications.
The web service interface Manage Engineering Change Order In offers the operations CREATE_ECO and READ_ECO.
Action codes represent an instruction to the recipient of the web service request to process transmitted message node elements.
| Action Code | Description |
|---|---|
| 01 | Create; the system returns an error message if the node element already exists. |
| 02 | Update; the system returns an error message if the node element does not exist. |
| 03 | Delete; the system returns an error message if the node element does not exist. |
| 04 | Save; the system creates or changes the node element data. |
| 05 | Remove; the system deletes the node element. If the node element does not exist, the system does not send an error message. |
| 06 | No Action; the system does not change the node element. |
Default action code: 04 (Save).
Note: Action code 04 (Save) creates business documents if the system cannot identify a matching target business document. This applies if no business document ID or UUID is provided by the web service consumer. The web service consumer (external application) is responsible for providing correct business document IDs or UUIDs and to avoid accidental creation of duplicate business documents.
Show full documentation
Show full documentation