Used as base class for total order value and shared value between order customers

In some cases, when the property is "nillable", i.e. /NillableString, NillableDate, NillableShort, NillableLong or NillableDecimal) it is possible to clear/reset the value of a property (effectively setting the associated database field value to null) by setting the nil attribute to true and not providing any value.

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete
AM - N/A.

If action is "Delete", only key-field(s) are mandatory.
Key(s) = cuadrAdrid

In some cases, when the property is "nillable", i.e. /NillableString, NillableDate, NillableShort, NillableLong or NillableDecimal) it is possible to clear/reset the value of a property (effectively setting the associated database field value to null) by setting the nil attribute to true and not providing any value.

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete
AM - Add if non existing, else Modify.

If action is "Delete", only key-field(s) are mandatory.
Key(s) = bcPeriod and bcLpcode

If action is "Delete", only key-field(s) are mandatory.
Key(s) = buiYear

Models the intention to update a customer-contact. Most fields/elements in this object are optional and when left out, the corresponding property will be left unchanged. If a value is provided, the corresponding property will be updated to that specified value.

In some cases, when the property is "nillable", i.e. /NillableString, NillableDate, NillableShort, NillableLong or NillableDecimal) it is possible to clear/reset the value of a property (effectively setting the associated database field value to null) by setting the nil attribute to true and not providing any value.

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete
AM - Add if non existing, else Modify.

If action is "Delete", only key-field(s) are mandatory.
Key(s) = cucoContid

Key(s) = saplActid

If action is "Delete", only key-field(s) are mandatory.
Key(s) = cdhDealno, cdhHistlevel, cdhLpcode

If action is "Delete", only key-field(s) are mandatory.
Key(s) = cduDealId, cduDatemin, cduIntervalmin

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete
AM - Add if non existing, else Modify.

If action is "Delete", only key-field(s) are mandatory.
Key(s) = cesnCuescode

If action is "Delete", only key-field(s) are mandatory.
Key(s) = cuagAgencyno and cuagCategory

In some cases, when the property is "nillable", i.e. /NillableString, NillableDate, NillableShort, NillableLong or NillableDecimal) it is possible to clear/reset the value of a property (effectively setting the associated database field value to null) by setting the nil attribute to true and not providing any value.

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete
AM - N/A.

If action is "Delete", only key-field(s) are mandatory.
Key(s) = cubdId

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - N/A
D - Delete

If action is "Delete", only key-field(s) are mandatory.
Key(s) = cubrBransch

Note that AMD_TYPE MODIFY has no effect, this is because all properties are part of the key.

Most fields/elements in this object are optional and when left out, the corresponding property will be left unchanged. If a value is provided, the corresponding property will be updated to that specified value.

In some cases, when the property is "nillable", i.e. (NillabString, NillableDate, NillableShort, NillableLong or NillableDecimal) it is possible to clear/reset the value of a property (effectively setting the associated database field value to null) by setting the nil attribute to true and not providing any value.

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete
AM - Add if non existing, else Modify.

If action is "Delete", only key-field(s) are mandatory.
Key(s) = cueanId + cueanReferens

If action is "Delete", only key-field(s) are mandatory.
Key(s) = cuediEdicode

If action is "Delete", only key-field(s) are mandatory.
Key(s) = naAddrdetno

Most fields/elements in this object are optional and when left out, the corresponding property will be left unchanged. If a value is provided, the corresponding property will be updated to that specified value.

In some cases, when the property is "nillable", i.e. (NillabString, NillableDate, NillableShort, NillableLong or NillableDecimal) it is possible to clear/reset the value of a property (effectively setting the associated database field value to null) by setting the nil attribute to true and not providing any value.

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete
AM - Add if non existing, else Modify.

If action is "Delete", only key-field(s) are mandatory.
Key(s) = cupfPrflowcode

Key = Discount

Key = Discount

Key = odIssueDate

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete
AM - Add if non existing, else Modify.

If action is "Delete", only key-field(s) are mandatory.
Key(s) = odIssueDate

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete
AM - Add if non existing, else Modify.

If action is "Delete", only key-field(s) are mandatory.
Key(s) = orPacode and orPricelist

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete

If action is "Delete", only key-field, delCorrectionCode and delComment are mandatory.
Key(s) = mcjId

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete

If action is "Delete", only key-field(s) are mandatory.
Key(s) = custno

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete

If action is "Delete", only key-field, delCorrectionCode and delComment are mandatory.
Key(s) = mcjId

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete

If action is "Delete", only key-field(s) are mandatory.
Key(s) = mcjolId

This is a AMD-object, i.e. This object is used for ADD or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - NOTE! Not allowed, you can only add and remove adspaces..
D - Delete

If action is "Delete", only key-field, delCorrectionCode and delComment are mandatory.
Key(s) = advId

An orderline can be one of these types: ONLINE or LINEITEM, this is determined by the type-property.

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete

If action is "Delete", only key-field are mandatory.
Note!Depending on system settings delCorrectionCode and delComment may also be mandatory when deleting an orderline.
Key(s) = index

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete

If action is "Delete", only key-field are mandatory.
Key(s) = date

• the entity is left-out (completely undefined), meaning it should be initialized to a suitable default value in a create operation, and not affect existing data in an update operation.
• the entity is explicitly defined as NIL to reset existing data to a uninitialized state (usually null in the database).
• the entity is defined with a value to store or update existing data with.

NOTE: It is not allowed for a nillable to be both NIL and have a non-null value, or to have a null value and be defined as not NIL.

Create Examples:

 <!-- Use the default date -->
 <!-- <date /> -->
 
 <!-- Explicitly set date to an undefined (null) value -->
 <date nil="true" />
 
 <!-- Use a specific date value -->
 <date>2012-11-29T00:00:00+01:00</date>
 

 <!-- Do not update the date -->
 <-- <date /> -->
 
 <!-- Explicitly reset date to an undefined (null) value -->
 <date nil="true" />
 
 <!-- Update the date to a new value -->
 <date>2013-01-06T00:00:00+01:00</date>
 

• the entity is left-out (completely undefined), meaning it should be initialized to a suitable default value in a create operation, and not affect existing data in an update operation.
• the entity is explicitly defined as NIL to reset existing data to a uninitialized state (usually null in the database).
• the entity is defined with a value to store or update existing data with.

NOTE: It is not allowed for a nillable to be both NIL and have a non-null value, or to have a null value and be defined as not NIL.

Create Examples:

 <!-- Use the default integer value -->
 <!-- <decimal /> -->
 
 <!-- Explicitly set integer to an undefined (null) value -->
 <decimal nil="true" />
 
 <!-- Use a specific integer value -->
 <decimal>12345.67</decimal>
 

 <!-- Do not update the integer -->
 <-- <decimal /> -->
 
 <!-- Explicitly reset integer to an undefined (null) value -->
 <decimal nil="true" />
 
 <!-- Update the integer to a new value -->
 <decimal>123.456</decimal>
 

• the entity is left-out (completely undefined), meaning it should be initialized to a suitable default value in a create operation, and not affect existing data in an update operation.
• the entity is explicitly defined as NIL to reset existing data to a uninitialized state (usually null in the database).
• the entity is defined with a value to store or update existing data with.

NOTE: It is not allowed for a nillable to be both NIL and have a non-null value, or to have a null value and be defined as not NIL.

Create Examples:

 <!-- Use the default integer value -->
 <!-- <long /> -->
 
 <!-- Explicitly set integer to an undefined (null) value -->
 <long nil="true" />
 
 <!-- Use a specific integer value -->
 <long>1234567890</long>
 

 <!-- Do not update the integer -->
 <-- <long /> -->
 
 <!-- Explicitly reset integer to an undefined (null) value -->
 <long nil="true" />
 
 <!-- Update the integer to a new value -->
 <long>1337</long>
 

• the entity is left-out (completely undefined), meaning it should be initialized to a suitable default value in a create operation, and not affect existing data in an update operation.
• the entity is explicitly defined as NIL to reset existing data to a uninitialized state (usually null in the database).
• the entity is defined with a value to store or update existing data with.

NOTE: It is not allowed for a nillable to be both NIL and have a non-null value, or to have a null value and be defined as not NIL.

Create Examples:

 <!-- Use the default integer value -->
 <!-- <short /> -->
 
 <!-- Explicitly set integer to an undefined (null) value -->
 <short nil="true" />
 
 <!-- Use a specific integer value -->
 <short>8080</short>
 

 <!-- Do not update the integer -->
 <-- <short /> -->
 
 <!-- Explicitly reset integer to an undefined (null) value -->
 <short nil="true" />
 
 <!-- Update the integer to a new value -->
 <short>-1</short>
 

• the entity is left-out (completely undefined), meaning it should be initialized to a suitable default value in a create operation, and not affect existing data in an update operation.
• the entity is explicitly defined as NIL to reset existing data to a uninitialized state (usually null in the database).
• the entity is defined with a value to store or update existing data with.
  (The string value could be empty, but it is the same as null in an Oracle database)

NOTE: It is not allowed for a nillable to be both NIL and have a non-null value, or to have a null value and be defined as not NIL.

Create Examples:

 <!-- Use the default string value -->
 <!-- <string /> -->
 
 <!-- Explicitly set string to an undefined (null) value -->
 <string nil="true" />
 
 <!-- Use a specific string value -->
 <string>Novice</string>
 

 <!-- Do not update the string -->
 <-- <string /> -->
 
 <!-- Explicitly reset string to an undefined (null) value -->
 <string nil="true" />
 
 <!-- Update the string to a new value -->
 <string>Expert</string>
 

It contains the customer related mappings of the order. In order to create or update an orderKund there are other representations in the ws-api to use.

It contains the customer related mappings of the order.

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete
AM - Add if non existing, else Modify.

If action is "Delete", only key-field(s) are mandatory.
Key(s) = okCustno

It contains the LegelPerson related customer commission for an orderKund

It contains the customer commission related mappings of the order.

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete
AM - Add if non existing, else Modify.

If action is "Delete", only key-field(s) are mandatory.
Key(s) = okCustno

It contains the Salesmen related mappings of the order. In order to create or update an Salesmen share amount for order.

It contains the Salesmen related mappings of the order. In order to create or update an Salesmen share amount for order.

Keys = orPacode and orPricelist

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete
AM - Add if non existing, else Modify.

If action is "Delete", only key-field(s) are mandatory.
Key(s) = orPacode and orPricelist

Key = orPlcode

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete
AM - Add if non existing, else Modify.

If action is "Delete", only key-field(s) are mandatory.
Key(s) = orPlcode

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete
AM - Add if non existing, else Modify.

If action is "Delete", only key-field(s) are mandatory.
Key(s) = opPrflowcode

Logic for detecting customer creation and deletion.

 Create: 
 - cuhWhat    = "CU_CUSTNO" 
 - cuhCustno  = New customer no. 
 - cuhOldvalue= Null 
 - cuhNewvalue= New customer no.
 
 Delete: 
 - cuhWhat    = "CU_CUSTNO" 
 - cuhCustno  = Null 
 - cuhOldvalue= Deleted customer no.
 - cuhNewvalue= Null
 

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete
AM - Add if non existing, else Modify.

If action is "Delete", only key-field(s) are mandatory.
Key(s) = ocServcode and ocOcdate

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
D - Delete
.

If action is "Delete", only key-field(s) are mandatory.
Key(s) = cusSynonym

Note that AMD_TYPE MODIFY has no effect, this is because all properties are part of the key.