One predefined data validation rule is a logical rule set that contains one or more predefined error codes. The predefined error codes and associated error messages are visible in the UI and are intended to help you find the root cause of the problem.
For example, a predefined data validation rule is to check the functional exchange rate and contains only one error code. If the exchange rate of a transaction line fails this validation rule, this transaction line will be marked with the associated error code in Errors - Transactions tab (Data Interface > Inbound Integration). Another predefined data validation is to check whether the mandatory fields are present for the transaction lines and contains multiple error codes. If a transaction line fails this validation rule, you can tell which mandatory field is missing according to different error codes.
In version 36.010.00 or later, there are 37 enabled, 14 disabled, and 11 deprecated error codes. As the product evolves over time, new validation codes might be added, previously disabled codes might be enabled, and previously enabled codes might be disabled or even deprecated.
This article provides the complete lists of enabled, disabled, and deprecated error codes in the latest version.
Any changes to the predefined error codes in future releases will be explicitly announced in the release notes.
View validation rules
You can view the validation rules and the associated error messages in the UI.
- To view the validation rules, navigate to Setups > Stage Validation. Both predefined and customized validation rules are listed on the page. For the predefined validation rules, you cannot edit the conditions that are set up for the rule. However, you can edit the filter in the rule to filter out the transaction lines to which the validation rule should be applied.
- To view the predefined error code and associated error message for data validation, navigate to Setups > Application > Error Setup. The predefined error codes are listed as the standard type and have the prefix of RPRO. They are not editable.
Enabled error codes
The following table lists all the enabled error codes in version 36.010.00 or later:
- Error code: This column lists the error code of each validation rule. The transaction that fails the validation will be marked with the identified error codes in the UI.
- Explanation: This column describes the errors in the transaction data that are identified during the data validation process.
Only correct transaction data can be collected by Zuora Revenue. The transactions that fail the data validation process will stay in Zuora Revenue staging table and cannot be collected. Navigate to Data Interface > Inbound and click the Errors - Transactions tab to find the problematic transactions. Fix the errors in the upstream system and upload the transaction data again to Zuora Revenue.
|RPRO-00001||The transaction type is invalid. Valid values for the transaction type include SO, CT, INV, CM, CM-C, CM-R, CST, RORD, and CM-RO.|
The CV_Eligible flag value is invalid. Valid values include Y, N, or blank.
|RPRO-00007||The invoice quantity value is not specified. The invoice quantity value cannot be empty for the INV, CM, CM-C, CM-R, and CM-RO transaction types.|
|RPRO-00009||The specified currency code is wrong or the decimals of the selling price or list price are wrong.|
|RPRO-00011||The functional exchange rate is not 1 when the transaction currency is the same as the functional currency.|
|RPRO-00012||The global exchange rate is not 1 when the transaction currency is the same as the reporting currency.|
|RPRO-00013||The start date is later than the end date. The start date must be earlier than the end date.|
|RPRO-00014||The start date is blank for the credit memo transactions with the fixed duration credit rule. The start date is required for this type of credit memos.|
|RPRO-00015||The start date is earlier than December 31, 1947. The start date cannot be earlier than the year 1947.|
|RPRO-00018||The duration is specified, however, the start date is absent. The start date is required when you specify the duration field.|
|RPRO-00030||The original SO line ID is not specified for the RORD transactions. The original SO line ID is a mandatory field for the RORD transactions.|
|RPRO-00035||The invoice number is missing for the INV, CM, CM-C, CM-R, or CM-RO transactions. The invoice number is a mandatory field for these transaction types.|
|RPRO-00036||The invoice line ID is missing for the INV, CM, CM-C, CM-R, or CM-RO transactions. The invoice line ID is a mandatory field for these transaction types.|
|RPRO-00043||The cost functional exchange rate is not 1 when the functional currency is the same as the functional currency.|
|RPRO-00044||The cost global exchange rate is not 1 when the functional currency is the same as the reporting currency.|
|RPRO-00045||The specified cost currency code is wrong or the decimals of the cost amount are wrong.|
|RPRO-00046||The specified credit rule is invalid. Valid values are P, L, F, or blank.|
|RPRO-00047||The credit rule is specified for the standalone credit memo transactions. If the credit memo is not associated with any invoice or sales order line, the credit rule must be blank.|
|RPRO-00048||The specified cost type is invalid. Valid cost types are defined in the cost setup.|
The specified Unbill flag is invalid. Valid values are Y, N, or blank.
|RPRO-00051||The customer number is missing.|
The SSP Eligible flag is invalid. Valid values are Y, N, or blank.
|RPRO-00056||The specified impairment type is invalid. Valid values are CONTRACT IMPAIRMENT, NEW POB, or blank.|
|RPRO-00059||The extended selling price is missing.|
|RPRO-00063||The end date is blank for the credit memo transactions with the fixed duration credit rule. The end date is required for this type of credit memos.|
|RPRO-00066||The contract modification date is earlier than the SO book date. The contract modification date must be later than the SO book date.|
|RPRO-00067||The exchange rate is a negative value.|
|RPRO-00068||The duration or term value is negative.|
|RPRO-00072||The SO quantity field is 0 or blank.|
|RPRO-00073||The functional exchange rate is blank when the functional currency is different from the transaction currency.|
|RPRO-00074||The cost functional exchange rate is blank when the cost currency is different from the functional currency.|
|RPRO-00075||The specified start date and end date does not match the specified duration.|
|RPRO-00076||The transaction currency, company code currency, and the reporting currency are different in the system settings, however, the functional exchange rate (F_EX_RATE) and the reporting exchange rate (G_EX_RATE) fields are not specified for the transaction line.|
|RPRO-00077||The exchange rate of the SO update line is changed compared with the exchange rate of the original SO line. If the revenue of the original SO line has been recognized, the SO update line cannot be processed.|
|RPRO-00078||This positive and negative sign of the invoice amount does not match the sign of the SO line. The invoice line cannot be processed.|
|RPRO-00079||When the SO update line comes in contract revision timelines and the CV eligible flag is changed in the SO update line, if the contract treatment is prospective, the SO update line cannot be processed.|
|RPRO-00080||An invoice line is associated with different SO lines, the invoice line cannot be processed.|
Disabled validation codes
The following table lists all the disabled error codes in version 36.010.00 or later:
|RPRO-00020||The account segment or the segment delimiter is invalid in the Deferred Segments field.|
|RPRO-00021||The Accounting Segment field must be present for all transaction types.|
|RPRO-00022||The account segment or the segment delimiter is invalid in the Revenue Segments field.|
|RPRO-00023||The Revenue Segments field is blank.|
|RPRO-00033||The Sales Order Date field is blank.|
|RPRO-00039||The account segment or the segment delimiter is invalid in the Cost Def Segments field.|
|RPRO-00040||The Cost Def Segments field is blank.|
|RPRO-00041||The account segment or the segment delimiter is invalid in the Cost Rev Segments field.|
|RPRO-00042||The Cost Rev Segments field is blank.|
|RPRO-00061||The account segment or the segment delimiter is invalid in the Rev Offsets Segments field.|
|RPRO-00062||The account segment or the segment delimiter is invalid in the Def Offsets Segments field.|
|RPRO-00069||The FV date is later than the end date of the current open period.|
|RPRO-00070||The Rev Account Segments or the Def Account Segments field is invalid.|
|RPRO-00071||The Cost account segments field is invalid.|
Deprecated validation codes
The following table lists all the deprecated error codes in version 36.010.00 or later:
|RPRO-00003||The Customer Name field is blank.|
|RPRO-00006||The Line Item Num field is blank.|
|RPRO-00016||The End Date is earlier than December 31, 1947.|
|RPRO-00019||The Standalone flag is not specified for the CM transaction lines.|
|RPRO-00024||The Contract Number is blank.|
|RPRO-00025||The Contract Line ID is not available in Zuora Revenue.|
|RPRO-00026||The Contract Line ID field is blank.|
|RPRO-00053||The Set of Book Id field is blank.|
|RPRO-00057||The Original SO Line ID field is not specified for the CM transaction lines.|
|RPRO-00058||The Extended Sell Price is positive for the CM or RORD transaction lines.|
|RPRO-00065||The CT Line ID field is not available for the SO transaction lines in Zuora Revenue.|