Documentation

Requisite Fields



tr>
Name Description Read Write
General entity details (requisites)
ID Requisite ID. Created automatically and is unique within the database. YesNo
ENTITY_TYPE_ID Parent type entity ID. Possible types: "Company", "Contact". Required field.

Note: Parent type IDs for CRM entities are returned by ерпу method crm.enum.ownertype.
YesYes
ENTITY_ID Parent entity ID. Required field. YesYes
PRESET_ID Requisite template ID. Required field. YesYes
DATE_CREATE Date when created. YesNo
DATE_MODIFY Date when modified. YesNo
CREATED_BY_ID ID of requisite creator. YesNo
MODIFY_BY_ID ID of the requisite modifier. YesNo
NAME Requisite name. YesYes
CODE Requisite symbolic code. YesYes
XML_ID External key used for transfer operations. Object ID in external database. Field designation can be modified by the end developer. YesYes
ACTIVE Activity status. YesYes
SORT Sorting. YesYes
RQ_NAME Full name YesYes
RQ_FIRST_NAME First name YesYes
RQ_LAST_NAME Last name YesYes
RQ_COMPANY_NAME Abbreviated company name. YesYes
RQ_COMPANY_FULL_NAME Full company name. YesYes
RQ_COMPANY_REG_DATE Date of state registration. YesYes
RQ_DIRECTOR General dictator YesYes
RQ_ACCOUNTANT Chief accountant. YesYes
RQ_CEO_NAME CEO full name. YesYes
RQ_CEO_WORK_POS CEO position. YesYes
RQ_CONTACT Contact person. YesYes
RQ_EMAIL E-Mail. YesYes
RQ_PHONE Phone number. YesYes
RQ_FAX Fax. YesYes
RQ_IDENT_DOC ID document type. YesYes
RQ_IDENT_DOC_SER Series. YesYes
RQ_IDENT_DOC_NUM Number. YesYes
RQ_IDENT_DOC_DATE Date of issue. YesYes
RQ_IDENT_DOC_ISSUED_BY Issued by. YesYes
RQ_IDENT_DOC_DEP_CODE Department code. YesYes
RQ_INN TIN. YesYes
RQ_KPP KPP. YesYes
RQ_USRLE Handelsregisternummer (for DE). YesYes
RQ_IFNS IFNS. YesYes
RQ_OGRN OGRN. YesYes
RQ_OGRNIP OGRNIP. YesYes
RQ_OKPO OKPO. YesYes
RQ_OKTMO OKTMO. YesYes
RQ_OKVED OKVED. YesYes
RQ_EDRPOU EDRPOU. YesYes
RQ_DRFO DRFO. YesYes
RQ_KBE KBE. YesYes
RQ_IIN TIN. YesYes
RQ_BIN BIN. YesYes
RQ_VAT_PAYER VAT payer (for UA). YesYes
RQ_VAT_ID VAT ID (VAT payer ID). YesYes
RQ_VAT_CERT_SER VAT certificate series. YesYes
RQ_VAT_CERT_NUM VAT certificate series. YesYes
RQ_VAT_CERT_DATE Date of VAT certificate. YesYes
RQ_RESIDENCE_COUNTRY Residence country. YesYes
ORIGINATOR_ID External database ID. Field designation can be modified by the end developer. YesYes
Bank details (requisites)
ID Requisite ID. Created automatically and is unique within the database. YesNo
ENTITY_TYPE_ID Parent type entity ID. Default type: "Requisite". Required field.

Note: Parent type IDs for CRM entities are returned by ерпу method crm.enum.ownertype.
YesYes
ENTITY_ID Parent entity ID. Required field. YesYes
PRESET_ID Requisite template ID. Required field. YesYes
DATE_CREATE Date when created. YesNo
DATE_MODIFY Date when modified. YesNo
CREATED_BY_ID ID of requisite creator. YesNo
MODIFY_BY_ID ID of the requisite modifier. YesNo
NAME Requisite name. YesYes
CODE Requisite symbolic code. YesYes
XML_ID External key used for transfer operations. Object ID in external database. Field designation can be modified by the end developer. YesYes
ACTIVE Activity status. YesYes
SORT Sorting. YesYes
RQ_BANK_NAME Bank name. YesYes
RQ_BANK_ADDR Bank address. YesYes
RQ_BANK_ROUTE_NUM Bank Routing Number. YesYes
RQ_BIK BIK. YesYes
RQ_MFO MFO. YesYes
RQ_ACC_NAME Bank Account Holder Name. YesYes
RQ_ACC_NUM Bank Account Number. YesYes
RQ_IIK IIK. YesYes
RQ_ACC_CURRENCY Account currency. YesYes
RQ_COR_ACC_NUM Correspondent account. YesYes
RQ_IBAN IBAN. YesYes
RQ_SWIFT SWIFT. YesYes
RQ_BIC BIC. YesYes
COMMENTS Comment. YesYes
ORIGINATOR_ID External database ID. Field name can be modified by the end developer. YesYes
Requisite templates
ID Requisite ID. Created automatically and is unique within the database. YesNo
ENTITY_TYPE_ID Parent type entity ID. Required field.

Note: Parent type IDs for CRM entities are returned by ерпу method crm.enum.ownertype.
YesYes
COUNTRY_ID Country that matches with set of requisite template fields. YesYes
DATE_CREATE Date when created. YesNo
DATE_MODIFY Date when modified. YesNo
CREATED_BY_ID ID of the requisite creator. YesNo
MODIFY_BY_ID ID of the requisite modifier. YesNo
NAME Requisite name. YesYes
XML_ID External key, used for transfer operations. Object ID in external database. Field designation can be modified by the end developer. YesYes
ACTIVE Activity status. YesYes
SORT Sorting. YesYes
Requisite template fields
ID Requisite ID. Created automatically and is unique within the requisite. YesNo
FIELD_NAME Field name. YesYes
FIELD_TITLE Alternative field name for requisite. YesYes
SORT Sorting. YesYes
IN_SHORT_LIST Show in short list. YesYes
Requisite addresses
TYPE_ID Address type ID. Required field. "Address type" list item.

Note: "Address type" list items are returned by the method crm.enum.addresstype.
YesYes
ENTITY_TYPE_ID Parent entity type ID. Possible types: "Requisite", "Company", "Contact", "Lead". Required field.

Note: IDs of CRM entity types are returned by crm.enum.ownertype.
YesYes
ENTITY_ID Parent entity ID. Required field. YesYes
ADDRESS_1 Street, building, house. YesYes
ADDRESS_2 Apartment / office. YesYes
CITY City. YesYes
POSTAL_CODE Zip code. YesYes
REGION District. YesYes
PROVINCE Region. YesYes
COUNTRY Country. YesYes
COUNTRY_CODE Country code. YesYes
ANCHOR_TYPE_ID Parent entity, binded to the current entry.

Note: Only Contact or Company can be a parent entity for a Requisite. And only Requisite can be a Parent entity for Bank requisite. Addresses can be binded to Requisites. Addresses can be binded with Contacts or Companies Only for the purposes of backward compatibility. However, this binding is possible only on legacy accounts that have an old mode of handling addresses specifically enabled by technical support.
Note: These fields are used for service purposes only. They are needed to solve performance issues in selections of senior entities (Companies/Contacts) in CRM items that are not directly, but indirectly associated with such entities via other CRM items. When an Address entry is added, a direct binding of an address to senior entity - ENTITY_ID, ENTITY_TYPE_ID - is specified. For example, a Requisite: address entry fields ANCHOR_TYPE_ID and ANCHOR_ID automatically specify binding to more senior entity of the Requisite itself - Company/Client.
YesYes
ANCHOR_ID YesYes

User Comments

User comments are not part of official documentation. Use information provided by other users in the comments at your own risk.

The User Comments section is not to be used as a feature discussion board. Only registered users can post comments. Your comment will be visible once it has been approved by the moderator.
© «Bitrix Inc.», 2001-2019, «Bitrix Inc.», 2019