Search This Blog

Monday, March 15, 2010

03-12-2010

At Beth's suggestion, using the 8066 SOVL5 credentials provides better data.
If the gender code is M, F or U, then following applies:
  • INST_NBR - required, the field mapping says it is treated as a comment, but the tool pre-populates the value. If you don't send it, none of the error codes are non-zero but I can't imagine that anything worked. Get a RETURN_CODE of 72.

  • RQ_BANK_ID - required, field mappings say it is required and the tool pre-populates the value.
  • RQ_BRANCH_NBR - required, field mappings say it is required and the tool pre-populates the value.
  • RQ_OPR_NBR - required, field mappings say it is required and the tool pre-populates the value.
  • RQ_FIRST_NAME - required, if don't fill it in you get error codes and a navigation message stating that the name is missing. If you fill it in, you get a navation message saying that the last name is required.
  • RQ_LAST_NAME - required, if you fill it in you are told that the gender is missing.
  • RQ_GENDER_CODE - required, it is also used as a condition for other fields to be required. For example, using O as a gender requires that a business address be filled in
  • RQ_FOREIGN_IND - required
  • RQ_PERSONAL_BANKER_IND - required
  • RQ_ESTATE_IND - required
  • RQ_GOVERNMENT_IND - required
  • RQ_BANK_IND - required
  • RQ_PROBLEM_CUST_IND - required
  • RQ_BANK_EMPLOYEE_IND - required
  • RQ_DECEASED_IND - required
  • RQ_CLASSIC_BANKER_IND - required
  • RQ_NON_CUSTOMER_IND - required
  • RQ_DISCOUNT_BROKER_IND - required
  • RQ_SR_CITIZEN_IND - required
  • RQ_STOCKHOLDER_IND - required
  • RQ_CLASSIC_BANKER_IND - required
If the gender is defined as O, the following are also required:
  • RQ_ORGANIZATION_NAME - required
  • RQ_FIRST_NAME - illegal
  • RQ_LAST_NAME - illegal

No comments:

Post a Comment