InventoryLocations

This component runs the Inventory Locations (ILC) function.

Methods

Closed
Driver Type: SASI
Use this method to change the status of one or more inventory locations to Closed.
Create
Driver Type: SASI
Use this method to create an inventory location. If an inventory location already exists, an error message is produced and the payload is rejected.
CreateAsDraft
Driver Type: SASI
Use this method to create one or more draft inventory locations.
CreateOrAmend
Driver Type: SASI
Use this method to create or amend one or more inventory locations. An inventory location is created if it does not exist and amended if it does. Whereas both the Create and Amend methods require you to know in advance if an inventory location exists, this method can be used if you are unsure.
Delete
Driver Type: SASI
Use this method to delete inventory locations.
Hidden
Driver Type: SASI
Use this method to change the status of one or more inventory locations to Hidden.
Open
Driver Type: SASI
Use this method to change the status of one or more inventory locations to Open.
Query
Driver Type: Export
Use this method to obtain inventory location details or to extract inventory location data from SunSystems.
SuspendedHeld
Driver Type: SASI
Use this method to change the status of one or more inventory locations to Suspended/Held.

Mandatory fields

  • When creating, amending or deleting an inventory location, a value must be supplied for Location Code - payload element <Location>.
  • When creating or amending inventory location account recognition codes, a value must be supplied for:
    • Account Recognition Code - payload element <AccountRecognitionCode>
    • Account Code - payload element <AccountCode>
  • When creating or amending inventory location storage characteristics, a value must be supplied for Characteristic Code - payload element <CharacteristicCode>
Note: At runtime the component validates the payload contents to ensure that the values supplied are correct. Various combinations of values may require other elements in the payload to be specified before the payload can be processed successfully.

Related data

  • Account Recognition Code
  • Storage Characteristics
  • Standard Text
  • Standard Text Language
The attachment of Standard Text is supported by these methods:
  • Create
  • CreateAsDraft
  • CreateOrAmend
If the standard text supplied in the payload does not exist then it is created. However, it is not possible to amend existing standard text by this means; existing standard text is attached by key only, and any non-key fields in the SSC payload are ignored. Standard text can be amended using the Standard Text Language Variants function from SunSystems or the SSC component StandardTextLanguageVariants.

The standard text to be attached is language specific and therefore must be included within the StandardTextLang part of the payload in order to be detected by the SSC component, as shown in the following example:

<InventoryLocations>
	...
		<StandardText>
			<StandardTextLang>
				<Description>Delivery</Description>
				<LanguageCode>1</LanguageCode>
				<Paragraph1>Follow the special Instructions on the Invoice</Paragraph1>
				<ShortHeading>Delivery</ShortHeading>
				<StandardTextClassCode>SALES</StandardTextClassCode>
				<StandardTextCode>DELIVERY</StandardTextCode>
			</StandardTextLang>
		</StandardText>
</InventoryLocations>