Skip to main content

Validation API for SMDS Vendor

Guidelines

  • Design-first approach to be followed for all the validation APIs
  • Reference data to be cached wherever needed
  • All validation errors should be added to the validation error list which should be sent once in the response

Vendor Validation API

Mandatory Fields:

  • Vendor Account Group
  • Contact Details

Reference Data required for:

  • Vendor Account Group

Contact Details Validations​

  • For each vendor account group, the following fields are mandatory:
    • Organization Name
    • Search Term 1
    • Country
    • City
    • Language
    • Street or PO Box
    • Preferred Communication
  • Country Rules for regex apply to the following fields
    • Postal Code
    • Region
    • Telecommunication
  • Reference Data needed for the following fields
    • Country
    • City
    • Region
    • Language
    • Preferred Communication
    • International Dialing Code
    • Telecommunication Types
    • Electronic Communication Types
  • Search Term 2 has to be alpha-numeric, only a combination of both alphabets and numbers will be accepted
  • Vendors are only allowed to be created under countries which are currently in active state in GEO
  • Region Specific Postal Code validation is not present, only country-level regex validation is there (Do we need to add this?)
  • Preferred communication must be present/linked before opting for it
  • Communication Numbers from countries other than the vendor’s country are accepted (Valid?)
  • Third-party service validations are not present for communication numbers and emails (Do we need to introduce this?)
  • Tax jurisdiction validation
  • Field level validations - Vendor Validation API Fields.xlsx

Tax and Control Validations​

  • Reference Data needed for the following validations
    • Party Classification Types (Industry to which the vendor belongs)
    • Trading Partner Types (Maersk South America Ltd, Damco Distribution Canada Inc, etc)
    • Tax Types
    • Tax Number Types
    • Tax Base Types
    • Tax Information Types (VAT, TAXNO1, etc)
  • Country rules on the following fields:
    • Vendor Classification (Ex - Mandatory for Indian vendors)
    • Tax Information Type (Ex - Tax3 GSTIN Registration number is mandatory for all vendor classifications except ‘Not Registered’)
    • Tax Information Value (Based on Tax Information Type)
  • Intercompany Activity (I/C Activity) is mandatory for Account Group ZICV and must be blank for other Account Groups
  • Trading Partner is mandatory for Account Group ZICV and must be blank for other Account Groups
  • Field level validations - Vendor Validation API Fields.xlsx

Address Language Version Validations​

  • For creating an address language version, the following fields are mandatory:
    • Language Version
    • Organization Name
    • Search Term 1
  • Reference data needed for the following fields:
    • Language Version (Currently Vendor supports 12 language versions)
  • Search Term 2 has to be alpha-numeric, only a combination of both alphabets and numbers will be accepted
  • All other fields don’t have any data-driven validations
  • Field level validations - Vendor Validation API Fields.xlsx

Bank Key Validations​

In Bank details there are multilevel validations are applicable

  • Mandatory Fields: Bank key Country Id Bank Account number
  1. Bank Key: Bank key will be validated calling MDM https://smdsvndrpprd.apmoller.net/smds-vendor-backend/rest/search/ejb/bankkey/validate Using MDM it will check bank key is exists or not If not we will get -Bank key 0JKHGFDFGHJK78654323456 is not valid. Please enter the valid bank ke
  2. Bank Details: Validating the bank details using power center Job https://smdsvndrpprd.apmoller.net/smds-vendor-backend/rest/data/vendor/bankdetails/validate/null
    1. bankAccountNumber- If it is not null then validate the bank number. For country India, Bank Account length must not be more than 18 alpha-numeric characters.
    2. iban: (optional) If it is not null then validate the IBAN number For country India, IBAN is not in use.<br\\\\>IBAN Number is invalid
    3. accountHolderName(optional): If it is not null then validate Account Holder Name Account Holder cannot have any special characters
    4. bankControlKey(optional): If it is not null then validate Contry Key For country India, Control key must be blank.
    5. referenceDetails(optional): If it is not null then validate Reference Details For country India, Control key must be blank.
    6. partnerBankType : optional No validation
  3. Note: it will call powercenter to validate the bank details : WS_SO1000A_SMDS_VNDR_ValidationBankDetails

Purchasing Org Validations​

  • Mandatory Fields: orderCurrency paymentTerms purchasingOrg

Needs to check the validations at PowerCenter side. WS_SO1000A_SMDS_VNDR_PartnerFunctionsOperation Reference: Vendor_CC_PO_Webservices and Validation.xlsx

Company Codes Validations​

  • Mandatory Fields: company code desc reconciliation account id payment terms Id payment methods id

If we fill mandatory fields, it will check cross tab validations on contact details.

  1. accountWVendor: if all mandatory fields are updated then it will check UI validation for one of the text filed. Account W/Vendor must not be null when mandatory fields are present. Account W/Vendor : AccountWVendor value must be E-INV-M, E-INV-Q, E-FINV Foreign Vendor, or NON-E-INV
  2. whTaxCountryId is a drop down and optional.
  3. If whTaxCountryId is selected, in whTaxCountryId Taxes Section
    1. liable - Liable is mandatory if tax type is populated.
    2. exemptTo- Exemption To must be completed if Exemption Certificate Number is completed.
    3. exemptFrom - Exemption From must be completed if Exemption Certificate Number is completed.
    4. exemptionRate- Format for Exemption Rate has to be \"nnn.nn\" / \"999.99\"
  4. clerkMail: Clerk email is invalid.
  5. clerkFax: Clerk Fax must be numeric.
  6. clerkPhone: No Validation Required

Reference: Vendor_CC_PO_Webservices and Validation.xlsx

Bank Validation API (Pending)

Was this page helpful?