CostObjectInformationPurpose indicates the type of update. The allowed values are: “FullUpdate” or “DeltaUpdate”. FullUpdate is the scenario for initial cost object uploads. The file contains all the organization’s cost objects meaning a “delete-insert” operation is executed in IBX eProcurement by this transaction. DeltaUpdate is the strongly recommended scenario for maintenance and additional costobjects to be uploaded to IBX eProcurement. Fewer amounts of data with a higher frequency and a faster upload are the advantages. Each CostObjectInformation document needs to have an identifier to be stored in this field. A sequence number can optionally be added to the CostObjectInformationNumber in this field. The document’s issue date is expressed as date plus timestamp with optional offset from GMT. (Format: YYYY-MM-DDTHH:MM:SS [[+-]HH:MM]). Example: 2011-03-12T06:35:03-06:00 The customer organization issuing the cost object information is identified by the Ident in the element //CostObjectInformationHeader/CostObjectIssuingOrganizationIdentifier with appropriate agency code = “AssignedByBuyerOrBuyersAgent” or “AssignedByMarketPlace”. The organization identifier in the document has to match a valid company code maintained in IBX eProcurement. In //CostObjectInformationDetail/ListOfCostObjects multiple CostObject items can be listed. Each cost object item contains information about the cost allocation object. Each combination of type and ID must be unique per document. The element CostObject as such is empty. The necessary information is provided as attributes. Obsolete attribute if customer is upgraded to SRM 7. In the meta-type and the subtype attribute the type of object for cost allocation is specified. In the SRM 4 setup in this attribute the type of object for cost allocation is specified - usually the same as in @subtype unless agreed differently between customer and IBX. Standard cost object types see @subtype. In the subtype attribute the type of object for cost allocation is specified. Standard cost object types are: AS = Asset number; CC = CostCenter; OR = Order; STR = Generic Cost Object; WBS = Project number ACCNO = GL account. Whether they are valid in IBX eProcurement depends on the customer's setup. The identifier for the costobject in the customer's ERP system is maintained in the subtype-id attribute. Cost object description in clear text. Note: the description for a cost object is only visible in IBX eProcurement for users who are logged on in the same language that is sent in subtype-language for that cost object. Language of the cost object description in ISO 639 code. IBX eProcurement User-ID (login) of the user responsible for the cost object, usually the approver. Cost object parent identifier as used by the customer. Obsolete attribute if customer is upgraded to SRM 7. In the SRM 4 setup in this attribute the type of cost object parent type is specified. See list of generally allowed types as for @subtype. Cost object parent type. See list of generally allowed types as for @subtype. Total budget allocated for the cost object. This value must be greater than the value in attribute subtype-spentbudget. Format: Numerical decimal. Decimal designator is a dot ("."). Must be present, if subtype-spentbudget is present. Already spent budget amount of the cost object. Format: Numerical decimal. Decimal designator is a dot ("."). Must be present, if subtype-totalbudget is present. Currency of the budget for the cost object. ISO 4217 codes, such as EUR, USD, etc. Must be present, if subtype-totalbudget is present. Code indicating whether the costobject shall be created, updated or deleted: "CREATE"; "UPDATE"; "DELETE". The attribute actioncode must be present if //CostObjectInformationHeader/CostObjectInformationPurpose/CostObjectInformationPurposeCoded = "DeltaUpdate". If a CostObject is sent with actioncode "CREATE" but the subtype-id already exists, the existing CostObject will be updated with the new information. If a CostObject is sent with actioncode UPDATE but the CostObject does not exist, the CostObject will be created. The attribute actioncode is not needed if //CostObjectInformationPurposeCoded = "FullUpdate" since in this case all cost objects of the issuing organization will first be deleted and then the ones provided in the document will be created. Indicator telling if the attest_acc table explicitly should not be updated. Format: X = Do not update. (Only applicable for customers on SRM 7.) Indicator telling if the zbbp_std_acc and zbbp_std_accd tables explicitly should not be updated. Format: X = Do not update. (Only applicable for customers on SRM 7.) Indicator telling if the zbudget_status table explicitly should not be updated. Format: X = Do not update. (Only applicable for customers on SRM 7.) The date from which the cost object is valid. This is optional and the logic in the IBX eProcurement system is to put it to the current date if not provided. Format: Date in format YYYYMMDD. (Only applicable for customers on SRM 7.) The date up until when the cost object is valid. This is optional and the logic in the eProcurement system is to put it to 99991231 if not provided. Format: Date in format YYYYMMDD. (Only applicable for customers on SRM 7.) The company code of the superior cost object. (Only applicable for customers on SRM 7.) The approval limit that the approver should use (overrides the user specific ones). Format: Numerical decimal. Decimal designator is a dot (“.”). (Only applicable for customers on SRM 7.) Currency of the provided approval limit. ISO 4217 codes, such as EUR, USD, etc. Must be present if approval-limit is present. (Only applicable for customers on SRM 7.) Indicator telling if the attest_acc table explicitly should not be updated. Format: X = Do not update. (Only applicable for customers on SRM 7.) Indicator telling if the zbbp_std_acc and zbbp_std_accd tables explicitly should not be updated. Format: X = Do not update. (Only applicable for customers on SRM 7.) Indicator telling if the zbudget_status table explicitly should not be updated. Format: X = Do not update. (Only applicable for customers on SRM 7.) The date from which the cost object is valid. This is optional and the logic in the IBX eProcurement system is to put it to the current date if not provided. Format: Date in format YYYYMMDD. (Only applicable for customers on SRM 7.) The date up until when the cost object is valid. This is optional and the logic in the eProcurement system is to put it to 99991231 if not provided. Format: Date in format YYYYMMDD. (Only applicable for customers on SRM 7.) The company code of the superior cost object. (Only applicable for customers on SRM 7.) The approval limit that the approver should use (overrides the user specific ones). Format: Numerical decimal. Decimal designator is a dot (“.”). (Only applicable for customers on SRM 7.) Currency of the provided approval limit. ISO 4217 codes, such as EUR, USD, etc. Must be present if approval-limit is present. (Only applicable for customers on SRM 7.)