ValueLabelsSetup

This component runs the Value Labels (VLB) function. It allows the user to create, amend and delete as well as query value labels.

Methods

Closed
Driver type: SASI
Use this method to change the status of a value label setup to Closed.
CreateAsDraft
Driver type: SASI
Use this method to create a draft value label setup.
CreateOrAmend
Driver type: SASI
Use this method to create or amend value labels. A value label is setup if it does not exist, and amended if it does.
CreateReplaceOrDelete
Driver type: SASI
Use this method to synchronize value labels. The value label is created if it does not exist already and replaced if it does. If the value label does not exist in the originating business unit, it is deleted.
Delete
Driver type: SASI
Use this method to delete value label(s) from SunSystems.
Hidden
Driver type: SASI
Use this method to change the status of a value label setup to Hidden.
Open
Driver type: SASI
Use this method to change the status of a value label setup to Open.
Query
Driver type: Export
Use this method to extract value label(s) from SunSystems 5.
Suspended/Held
Driver type: SASI
Use this method to change the status of a value label setup to Suspended/Held.

Mandatory fields

When creating / amending / deleting / extracting value label(s), you must supply Value Label - payload element <ValueLabelIdentifier>.

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

Standard Text
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:
<AnalysisCodes>					
		...
		<StandardText>		
				<StandardTextLang>
						<LanguageCode>1</LanguageCode>
						<StandardTextClassCode>STD</StandardTextClassCode>
						<StandardTextCode>DELIV</StandardTextCode>
				</StandardTextLang>
		</StandardText>
</AnalysisCodes>