Show full documentation

 Show full documentation

Definition

An interface to create, update or delete an organisational unit which can be used for organisational unit replication or migration.

Business Context and Use

The web service interface Manage Organisational Unit In enables you to connect external applications to your SAP system and to create and edit organisational units in your system. The web service interface Manage Organisational Unit In is relevant if your company wants to adopt the organisational management.

The web service interface Manage Organisational Unit In offers the operations MaintainBundle and CheckMaintainBundle.

Prerequisites

It is mandatory to have an overview about all needed adotion to the complete organisational model to be achieved by using this interface. Each call of the service Manage Organisational Unit In adoptes the organisational model of your company immediately. Each usage of the service Manage Organisational Unit In has to result in a consistent organisational model. Otherwise the processing cannot be finished successfully.

Example 1:

If you want to Create a tree of organisational units you've either to call the service Manage Organisational Unit In with one organisational unit after another starting with the root of the tree or by providing all organisational units of the complete tree as you otherwise might not linke the organisational units correctly.

Constraints and Integrity Conditions

General Rules for Using this Web Service

Check Maintain Bundle vs. Maintain Bundle

Maintain Bundle operations enable external applications to create and change business document data. Check Maintain Bundle operations enable external applications to simulate maintain bundle requests without changing business document data. In particular, Check Maintain Bundle operations have the following functions:

• Return system messages similar to corresponding maintain bundle operations

• Provide the same message type as the corresponding operation Maintain Bundle

• Do not assign internal numbers from a productive number range interval (number range statuses are not increased)

• Do not change business documents

Action Code

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.

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 in particular 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. This will avoid accidentally creating duplicate business documents.

List Processing

The processing of node elements with cardinality > 1 (for example, a list of quote items or contact of a Customer) can be controlled using List Complete Transmission Indicators (LCTI). The LCTI indicates whether a list of node elements is transmitted completely. The LCTI of a node element with cardinality > 1 is modeled as an attribute of its parent node element (attribute name: <name of child element>ListCompleteTransmissionIndicator).

LCTI	Description
false	The list of node elements is not completely transmitted. Hence, all node elements that are not transmitted remain unchanged. If transmitted node elements in the list can be uniquely identified, the system processes the node elements according to the action code. If transmitted node elements in the list cannot be uniquely identified, the system appends the node element to the corresponding list of node elements in the target business document.
true	The list of elements is completely transmitted. Hence, all node elements that are not transmitted are deleted. If no node element is transmitted, all the node elements in the system will be removed.

Default list complete transmission indicator: false.

Note: The LCTI refers to the completeness of the list of node elements and does not imply completeness of sub-elements.

Empty and Missing Elements

Optional leaf elements in request messages that are not transmitted within a web service request are not changed in corresponding business documents.

Communication Timeout

Maintain bundle and check maintain bundle operations are mass-enabled stateless synchronous web service operations. Transferring or requesting amounts of data that are too large can cause communication timeouts. The web service consumer is responsible for ensuring reasonable sizes of data for mass operations.

Message Header

Maintain bundle and check maintain bundle operations support exactly one execution (idem potency). To ensure exactly one execution of web service requests, the web service consumer has to provide unique values for the elements ID or UUID of the BasicMessageHeader node element.

Change State ID

Using change state identifier (element name ChangeStateID), external applications can ensure that a modifying operation is not executed because the state of the business document has changed since the external application last read its data.

The change state ID is an uninterpretable string that is provided by query and read operations and can be utilized by all modifying operations. If the change state identifier is provided when calling a modifying operation, the system does not perform the operation if the state of the business document instance has changed since the change state ID was computed. If the change state ID is not provided by the web service consumer, the system performs the web service operation without checking the state of the business document.

The web service consumer (external application) is responsible for preventing accidental changes to business documents.

Note: For this web service the change state ID does not apply to the ContactPerson, Relationship, CommunicationArrangement, DirectResponsibility, SalesArrangement, or PaymentData node elements.

Object Node Sender Technical Identifier

Request node elements with cardinality > 1 contain an object node sender technical identifier to relate response message elements and log items to corresponding node elements in the request message.

The object node sender technical identifiers are provided as ObjectNodeSenderTechnicalID in request message types and referred to as ReferenceObjectNodeSenderTechnicalID in corresponding response message types.

If the object node sender technical ID is initial, the object node sender technical ID of the parent node element in the request is returned as the reference object node sender technical ID. If the object node sender technical IDs of all parent node elements are initial, the reference object node sender technical ID is returned as initial as well.

Note: The values specified in the ObjectNodeSenderTechnicalID are transient values that establish the correspondence between elements for only a single call. The web service consumer is not required to specify them or to use the same values for different calls. Also, the service provider does not interpret these values at all. Instead, the service provider returns them to the web service consumer in the ReferenceObjectNodeSenderTechnicalID elements.

Note: The ObjectNodeSenderTechnicalID is also used to identify failed business document modifications in a mass operation.

Example

Request:

 
<Child>
    <ObjectNodeSenderTechnicalID>999_A<ObjectNodeSenderTechnicalID>
    <Content>Child A: Some correct content</Content>
</Child>
<Child>
    <ObjectNodeSenderTechnicalID>999_B<ObjectNodeSenderTechnicalID>
    <Content>Child B: Some erroneous content</Content>
</Child>

Response:

 
<Log>
    <Item>
        <ReferenceObjectNodeSenderTechnicalID>999_B </ReferenceObjectNodeSenderTechnicalID>
        <Note>Error message for Child B</Note>
    </Item>
</Log>

Response Message

The structure of the response message consists of two parts:

• A business document-specific part containing information about IDs and UUIDs of the created and changed business documents

• Log items containing system messages including errors, warnings, and information messages raised by the system during processing of the web service request

More Information

General Information

You can find general information about Web services, their structure and consumption in the Web Services documentation.

Scenarios

Possible scenarios include the following:

• Create an Organisational Unit

The MaintainBundle operation is used to create an organisational unit

• Update an organisational unit

The MaintainBundle operation is used to change an organisational unit

Example to create an organisational unit:

<n0:OrganisationalUnitBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
 <OrganisationalUnit actionCode="01">
  <ID>ZT-0001</ID>
  <ValidityPeriod>
   <StartDate>1999-01-24</StartDate>
   <EndDate>1999-01-24</EndDate>
  </ValidityPeriod>
  <NameAndAddress actionCode="01">
   <ValidityPeriod>
    <StartDate>1999-01-24</StartDate>
    <EndDate>1999-01-24</EndDate>
   </ValidityPeriod>
   <Name>ZTest</Name>
  </NameAndAddress>
  <ParentOrganisationalUnitAssignment actionCode="01">
   <ValidityPeriod>
    <StartDate>1999-01-24</StartDate>
    <EndDate>1999-01-24</EndDate>
   </ValidityPeriod>
   <ParentOrganisationalUnitID>ZT-0000</ParentOrganisationalUnitID>
  </ParentOrganisationalUnitAssignment>
  <EmployeeAssignment actionCode="01">
   <ValidityPeriod>
    <StartDate>1999-01-24</StartDate>
    <EndDate>1999-01-24</EndDate>
   </ValidityPeriod>
   <RoleCode>219</RoleCode>
   <EmployeeID>8000001190</EmployeeID>
   <JobID>SALESREPRESENTATIVE</JobID>
   <ReportingLineIndicator>true</ReportingLineIndicator>
   <FunctionalIndicator>true</FunctionalIndicator>
  </EmployeeAssignment>
 </OrganisationalUnit>
</n0:OrganisationalUnitBundleMaintainRequest_sync_V1>

Example to change an organisational unit:

For a change of an organisational unit it's important to know that it is not possible to change the validity of a subnode. If you need to change e.g. the employee assignment of a single employee you'll have to remove and reenter ALL employee assignments for that org unit! This can be done by using the *CompleteTransmissionIndicator for the corresponding node.

Let's assume we've an organisational unit ZT-0000 with a validity of 01.01.1999 till 28.02.1999 and an assigned employee responsible with ID 0001 for that validity.

We now want to delimit employee 0001 for january as employee 0002 will be assigned in february.

To do so we need to remove the existing assignments which is done by setting the CompleteTransmissionIndicator for the EmployeeAssignment to True. This will remove all existing assignments. In addition we've to transfer the new assignments for the organisational unit.

Please be careful doing so in productive systems as changes take effect immediately and errors can easily be made!

If needed retrieve the complete data of the subnode first to pass all relevant data again when using the CompleteTransmissionIndicators!

<n0:OrganisationalUnitBundleMaintainRequest_sync xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
 <OrganisationalUnit actionCode="04" employeeAssignmentListCompleteTransmissionIndicator="true">
  <ID>ZT-000</ID>
  <EmployeeAssignment actionCode="01">
     <ValidityPeriod>
    <StartDate>1999-01-01</StartDate>
    <EndDate>1999-01-31</EndDate>
   </ValidityPeriod>
   <EmployeeID>0001</EmployeeID>
   <JobID>SALESREPRESENTATIVE</JobID>
   <RoleCode>219</RoleCode>
   <ReportingLineIndicator>true</ReportingLineIndicator>
   <FunctionalIndicator>true</FunctionalIndicator>
  </EmployeeAssignment>
  <EmployeeAssignment actionCode="02">
     <ValidityPeriod>
    <StartDate>1999-02-01</StartDate>
    <EndDate>1999-02-28</EndDate>
   </ValidityPeriod>
   <EmployeeID>0002</EmployeeID>
   <JobID>SALESREPRESENTATIVE</JobID>
   <RoleCode>219</RoleCode>
   <ReportingLineIndicator>true</ReportingLineIndicator>
   <FunctionalIndicator>true</FunctionalIndicator>
  </EmployeeAssignment>
 </OrganisationalUnit>
</n0:OrganisationalUnitBundleMaintainRequest_sync>

 Show full documentation

 Show full documentation

No documentation available.

 Show full documentation

 Show full documentation

No documentation available.