Input Payload Element

Table 1. Payload elements
Element	Data Type	Description
`<SSC>`		Top-level element
`<User>`		User element
`<Name>`	Alphanumeric, length 3. Must be a valid SunSystems user.	User Name Specify the operator ID for the payload. This operator ID must be already set up in SunSystems using Security prior to executing the payload.
`<SunSystemsContext>`		Used to specify high-level information that is used at runtime to identify which business unit is to be used.
`<BusinessUnit>`	Alphanumeric, length 3. Must be a valid SunSystems user.	Specify the business unit that you wish to use. Note: If this element value is blank, the component defaults to the demonstration PKP business unit.
`<Payload>`		High-level element that is used to flag the start of the data. A payload file must only contain one `<Payload>` element.
`<Item>`		High-level element that is used to flag the start of an item data element. A payload file must contain at least one of these. There is no limit to the number of `<Item>` elements that can be present within a `<Payload>` element.
`<ItemCode>`	Mandatory. Alphanumeric, length 30.	The item code for which costs are to be created or amended.
`<Costs>`		High-level element that is used to flag the start of an Item Cost data element.
`<CostAnalysisId>`	Mandatory. Integer. Must already exist in SunSystems.	The cost analysis that these costs apply to. Up to nine different cost analysis can be set.
`<CostTypeCode>`	Mandatory. Alphanumeric, length 15. Must already exist in SunSystems.	The type of cost for the item, for example, goods cost, carriage, insurance or delivery. These must already have been set up using Inventory Cost Types (ICT), or by a previous SSC payload.
`<CurrencyCode>`	Mandatory. Alphanumeric, length 5. Must already exist in SunSystems.	The code for the currency that the costs are held in.
`<ItemUserDefinedCost>`		High-level element used to flag the start of an Item User Defined Cost data element.
`<DateTimeUserDefinedCost>`	Ignore.	The user defined cost may have a date associated with it such as the date it was set up or the date when it was last amended. If the value is present in the payload, it is ignored and system generated audit timestamp is used instead.
`<ItemUserDefinedValue>`	Mandatory. Numeric. Must be greater than zero and less than or equal to 9999999999999.99999.	The user defined cost for this item, currency, cost type and cost analysis combination.
`<Period>`	Mandatory. Numeric. Must be in format `pppyyyy` where `pppp` is the period and `yyyy` is the period year.	The period that the user defined cost belongs to. You can set up costs for different periods. For example, period 102001 has a user defined cost of 100 and in period 0112001 it has increased to 120.
`<Status>`	Ignore.	System generated. This is always set to 0 Open.
`<UserDefinedCostDefinitionCode>`	Mandatory. Alphanumeric, length 15. Must already exist in SunSystems.	The user defined cost definition code to be used. This must already have been set up using User Defined Inventory Cost (IUC).

<SSC>

Top-level element

<User>

User element

<Name>

Alphanumeric, length 3.

Must be a valid SunSystems user.

User Name

Specify the operator ID for the payload. This operator ID must be already set up in SunSystems using Security prior to executing the payload.

<SunSystemsContext>

Used to specify high-level information that is used at runtime to identify which business unit is to be used.

<BusinessUnit>

Alphanumeric, length 3.

Must be a valid SunSystems user.

Specify the business unit that you wish to use.

Note: If this element value is blank, the component defaults to the demonstration PKP business unit.

<Payload>

High-level element that is used to flag the start of the data. A payload file must only contain one <Payload> element.

<Item>

High-level element that is used to flag the start of an item data element. A payload file must contain at least one of these. There is no limit to the number of <Item> elements that can be present within a <Payload> element.

<ItemCode>

Mandatory.

Alphanumeric, length 30.

The item code for which costs are to be created or amended.

<Costs>

High-level element that is used to flag the start of an Item Cost data element.

<CostAnalysisId>

Mandatory.

Integer.

Must already exist in SunSystems.

The cost analysis that these costs apply to. Up to nine different cost analysis can be set.

<CostTypeCode>

Mandatory.

Alphanumeric, length 15.

Must already exist in SunSystems.

The type of cost for the item, for example, goods cost, carriage, insurance or delivery. These must already have been set up using Inventory Cost Types (ICT), or by a previous SSC payload.

<CurrencyCode>

Mandatory.

Alphanumeric, length 5.

Must already exist in SunSystems.

The code for the currency that the costs are held in.

<ItemUserDefinedCost>

High-level element used to flag the start of an Item User Defined Cost data element.

<DateTimeUserDefinedCost>

Ignore.

The user defined cost may have a date associated with it such as the date it was set up or the date when it was last amended. If the value is present in the payload, it is ignored and system generated audit timestamp is used instead.

<ItemUserDefinedValue>

Mandatory.

Numeric.

Must be greater than zero and less than or equal to 9999999999999.99999.

The user defined cost for this item, currency, cost type and cost analysis combination.

<Period>

Mandatory.

Numeric.

Must be in format pppyyyy where pppp is the period and yyyy is the period year.

The period that the user defined cost belongs to. You can set up costs for different periods. For example, period 102001 has a user defined cost of 100 and in period 0112001 it has increased to 120.

<Status>

Ignore.

System generated. This is always set to 0 Open.

<UserDefinedCostDefinitionCode>

Mandatory.

Alphanumeric, length 15.

Must already exist in SunSystems.

The user defined cost definition code to be used. This must already have been set up using User Defined Inventory Cost (IUC).