PaymentTermsGroups

This component runs the Paywment Terms (PYT) function.

It allows you to set up and maintain payment terms.

Note: If a set of payment terms changes, you should alter the terms using the SunSystems Payment Terms (PYT) function, or this component. The revised terms apply immediately to any new transactions entered using the terms code. The payment details on existing transactions that were determined by the previous payment terms code settings are not updated.

Methods

Closed
Driver Type: SASI
Use this method to change the status of one or more payment terms groups to Closed.
CreateAsDraft
Driver Type: SASI
Use this method to create one or more draft payment terms groups.
CreateOrAmend
Driver Type: SASI
Use this method to create or amend one or more payment terms groups. A payment terms group is created if it does not exist and amended if it does.
Hidden
Driver Type: SASI
Use this method to change the status of one or more payment terms groups to Hidden.
Open
Driver Type: SASI
Use this method to change the status of one or more payment terms groups to Open.
Query
Driver Type: Export
Use this method to obtain payment terms group details or to extract payment terms group data from SunSystems.
Suspended/Held
Driver Type: SASI
Use this method to change the status of one or more payment terms groups to Suspended/Held.

Mandatory fields

  • When creating or amending a payment terms group, a value must be supplied for Payment Terms Group Code - payload element <PaymentTermsGroupCode>
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
  • Standard Text Language

The attachment of Standard Text is supported by the CreateOrAmend and CreateAsDraft methods. 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:

<PaymentTermsGroups>
	...
		<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>
</PaymentTermsGroups>