eConnect schema

  • Article

Description

The base node for all eConnect documents. To create an eConnect XML document, add one or more of the following tranaction types.

Schema

  • <BRBankDepositsType >
  • <BRBankTransactionType>
  • <BRBankTransactionVoidType>
  • <BRDeleteBankDepositsType>
  • <BRPostBankDepositsType>
  • <CMPCreateBankType>
  • <CMPCreateCountryType>
  • <CMPCreditCardType>
  • <CMPInternetAddressType>
  • <CMPShippingMethodType>
  • <FACreateAccountGroupType>
  • <FACreateAssetBookIDType>
  • <FACreateAssetBookITCType>
  • <FACreateAssetClassIDType>
  • <FACreateAssetIDType>
  • <FACreateAssetInsuranceType>
  • <FACreateAssetLeaseType>
  • <FACreateAssetPurchaseType>
  • <FACreateAssetUserDataType>
  • <FACreateBookClassType>
  • <FACreateBookIDType>
  • <FACreateInsuranceClassIDType>
  • <FACreateLeaseCompanyType>
  • <FACreateLocationIDType>
  • <FACreatePhysicalLocationIDType>
  • <FACreateRetirementCodeType>
  • <FACreateStructureType>
  • <FSEquipmentType
  • <FSRMType>
  • <FSRTVType>
  • <FSServiceCallType>
  • <GLAccountType>
  • <GLCheckbookMasterType>
  • <GLCreateAccountCategoryType>
  • <GLCreateAccountCurrenciesType>
  • <GLFixedAllocationAccountType>
  • <GLTransactionType>
  • <GLVariableAllocationAccountType>
  • <HRApplicantEducationType>
  • <HRApplicantInterviewType>
  • <HRApplicantReferenceType>
  • <HRApplicantSkillType>
  • <HRApplicantTestType>
  • <HRApplicantType>
  • <HRApplicantWorkHistoryType>
  • <HRCreateSkillSetType>
  • <HRCreateTestType>
  • <HRDeleteApplicantApplicationType>
  • <HRDeleteApplicantEducationLineType>
  • <HRDeleteApplicantEducationType>
  • <HRDeleteApplicantInterviewType>
  • <HRDeleteApplicantReferenceLineType>
  • <HRDeleteApplicantReferenceType>
  • <HRDeleteApplicantRequisitionTYpe>
  • <HRDeleteApplicantTestLineType>
  • <HRDeleteApplicantTestType>
  • <HRDeleteApplicantType>
  • <HRDeleteApplicantWorkHistoryLineType>
  • <HRDeleteApplicantWorkHistoryType>
  • <HRDeleteRequistionType>
  • <HRDeleteSkillSetLineType>
  • <HRDeleteSkillSetType>
  • <HRDeleteSkillType>
  • <HRDeleteTestType>
  • <HRRequisitionType>
  • <HRSkillType>
  • <IVCreateItemCurrencyType>
  • <IVCreateItemPriceListType>
  • <IVCreateIVItemClassType>
  • <IVCreatePlannerType>
  • <IVCreatePriceGroupType>
  • <IVCreatePriceLevelType>
  • <IVCreateSiteBinType>
  • <IVCreateUOFMScheduleType>
  • <IVInventoryItemSiteType>
  • <IVInventorySiteType>
  • <IVInventoryTransactionType>
  • <IVInventoryTransferType>
  • <IVItemMasterType>
  • <IVLotCategoryType>
  • <IVMultibinBinToBinTransferType>
  • <IVVendorItemType>
  • <LBCreateLockboxBankDetailsType>
  • <LBCreateLockboxType>
  • <PAAccountsSetupType>
  • <PAChangeOrderType>
  • <PAContractBillingCycleType>
  • <PAContractsType>
  • <PAEmployeeExpenseType>
  • <PAEquipmentLogTransactionType>
  • <PAMiscLogExpenseType>
  • <PAProjectAccessListType>
  • <PAProjectBillingCyclesType>
  • <PAProjectBudgetMasterType>
  • <PAProjectEquipmentListType>
  • <PAProjectFeesType>
  • <PAProjectsType>
  • <PATimeSheetsType>
  • <PMCreateBuyerType>
  • <PMDeleteVendorAddressType>
  • <PMManualCheckType>
  • <PMScheduledPaymentsType>
  • <PMTransactionType>
  • <PMVendorAddressType>
  • <PMVendorMasterType>
  • <POPDocumentDeleteType>
  • <POPDocumentVoidType>
  • <POPEnterMatchInvoiceType>
  • <POPMapSitesType>
  • <POPReceivingsType>
  • <POPtoSOPLinkRemoveType>
  • <POPTransactionType>
  • <RMApplyType>
  • <RMCashReceiptsType>
  • <RMCreateCustomerItemsType>
  • <RMCreateParentIDType>
  • <RMCustomerAddressType>
  • <RMCustomerClassType>
  • <RMCustomerMasterType>
  • <RMDeleteCustomerAddressType>
  • <RMDeleteCustomerType>
  • <RMDeleteSalespersonType>
  • <RMParentIDChildType>
  • <RMProspectMasterType>
  • <RMSalespersonMasterType>
  • <RMScheduledPaymentsType>
  • <RMTerritoryMasterType>
  • <RMTransactionType>
  • <RMUnapplyTransactionType>
  • <RMVoidTransactionType>
  • <RQeConnectOutType>
  • <SMMdaType>
  • <SMTransactionBatchType>
  • <SOPDeleteDocumentType>
  • <SOPDeleteLineType>
  • <SOPDistributionsType>
  • <SOPLineComponentType>
  • <SOPProcessHoldMasterType>
  • <SOPProcessHoldType>
  • <SOPSerialType>
  • <SOPtoPOPTransactionType>
  • <SOPTransactionType>
  • <SOPVoidDocumentType>
  • <UPRComputerTrxType>
  • <UPRCreateBenefitType>
  • <UPRCreateDeductionType>
  • <UPRCreateDepartmentType>
  • <UPRCreateEmployeeAddressType>
  • <UPRCreateEmployeeBenefitType>
  • <UPRCreateEmployeeClassType>
  • <UPRCreateEmployeeDeductionType>
  • <UPRCreateEmployeeLocalTaxType>
  • <UPRCreateEmployeePayCodeType>
  • <UPRCreateEmployeeStateTaxType>
  • <UPRCreateEmployeeTaxType>
  • <UPRCreateEmployeeType>
  • <UPRCreateLocalTaxType>
  • <UPRCreateLocationType>
  • <UPRCreatePayCodeType>
  • <UPRCreatePositionType>
  • <UPRCreateShiftCodeType>
  • <UPRCreateSupervisorType>
  • <UPRCreateWorker_CompensationCodeType>
  • <UPRDeleteEmployeeAddresssType>
  • <UPRDeleteEmployeePayCodeType>
  • <UPRDeleteEmployeeType>
  • <UPRManualTrxType>

Remarks

An eConnect XML document must contain all nodes required to create a valid transaction. You cannot split the nodes for a single transaction across multiple XML documents. However, you can modify XML documents to your specific business needs. This allows you to combine related documents to create new types of master records.

For example, a customer could be combined with a sales transaction document. This functionality allows you to create an eConnect XML document that contains all the XML transaction types and nodes required for your customer sales document.

For additional information about using the <eConnect> schema to create eConnect XML documents. see eConnect XML Documents

Document structure

<eConnect>
</eConnect>