The following section provides information on designing with certain Application Adapters. If you have any questions or problems, see the Java CAPS web site at http://goldstar.stc.com/support.
This section covers the following topics:
Building an Oracle Applications Custom Pre-Validation Package.
Configuring the PeopleSoft Server for the PeopleSoft Adapter Projects.
The Sun Oracle Application scripts provided are intended to be used as a template or skeleton. You may need to modify these scripts to satisfy your own environment or requirements. These scripts have been tested successfully in the Sun environment.
This section covers the following information for building a custom Pre-Validation Package:
To view corresponding tables and scripts used for the Pre-Validation packages, refer to the following modules:
For Open Interfaces for which pre-validation scripts have been supplied, the SQL files shipped with the Adapter are sufficient for you to create a working Project. For Open Interfaces for which pre-validation scripts are not currently available, a template XML file (templateXml.xml) is supplied. Use this file to build your own pre-validation package. The procedure for you to follow is given in To Build a Custom Pre-Validation Package for a Non-Supported Open Interface.
The pre-validation scripts packaged with the Adapter for the supported modules are rudimentary and do not cover all possible scenarios. Since the requirements from Oracle occasionally change and evolve, you may be required to provide additional data and/or parameters to ensure that the Concurrent Manager request completes successfully and without errors. Pre-validation scripts have been tested in 11.5.3 only.
All pre-validation script packages (*_pkg.sql) contain the following procedures.
Table 1–1 Common Procedures
Procedure |
Purpose |
---|---|
Initialize_Profile |
Initializes the table for sharing to avoid running multiple instances by different users. |
TidyUp |
Updates sb_pass_or_fail columns in the staging table from INTERMEDIATE to PASS for records that were not marked as failed by the pre-validation rules. |
Validate |
The main validation procedure which calls the procedures that perform the pre-validations for the Interface Table. |
Modify the Oracle Applications master configuration file in the following location to add a new module:
<CAPS_Dir>/appserver/userdir/modules/ext/oracleappsadapter/ wizard/configs/Applications.xml |
When adding a new business function, assign the business section a new name and entry for the new open interface. Spaces are acceptable when creating a module name.
<Module Name=”Module_Name”Definition=”moduleDefinition.xml”> </Module> |
Notice that the name attribute is an English description which appears in the OTD wizard where the definition attribute locates the open interface XML definition file (this attribute cannot have spaces).
Copy and rename the template.xml file from the path to the appropriate directory:
<CAPS_Dir>/appserver/userdir/modules/ext/oracleappsadapter/ wizard/configs/templateXml.xml |
Appropriate directory:
<CAPS_Dir>/appserver/userdir/modules/ext/oracleappsadapter/wizard/ configs/business_function_name/moduleDefinition.xml |
where business_function_name is the name attribute value (for example, either Manufacturing or Financial).
While the template XML file does not have an error package or error table entries, you can look at any existing module to create these entries. If you choose to modify the common sb_install.sql file to append more errors for the new module, the SB_ERRORS table needs to be removed from the database so the wizard can recreate it with new error values the next time the wizard is run.
Replace the path with the correct open interface name.
<%%ORACLE_INTERFACE_NAME%%> |
Do not use spaces when creating an ORACLE_INTERFACE_NAME.
Replace the path with the correct business suite name.
<%%ORACLE_APPLICATION_SUITE NAME%%> |
Replace the path with the correct module name.
<%%MODULE_NAME%%> |
Do not use spaces when creating a MODULE_NAME.
The initialize and request_status scripts are already specified in the XML file. If you do not need these, simply remove them from the XML file. If you need to customize these scripts:
Copy the SQL file to the desired directory.
Rename the file—the package name must be the same as the SQL file name (which is true for all entries in this XML file).
Modify the scripts as needed for your own implementation.
In the XML file, refer to these new customized SQL files instead of the shipped SQL script.
Do not change either the Initialize_Profile stored procedure name, nor its location as the entry point for the initialization packages.
Replace <%%VALIDATION_PACKAGE_SQL_FILE_NAME%%> with the correct path and file name for the validation package. This validation package file name must be sql/business_function_name/<%%MODULE_NAME%%>/ <%%ORACLE_INTERFACE_NAME%%>/sb_validate_interfaceNameAbbreviation_pkg.sql, this path is relative from <CAPS_Dir>/edesigner/userdir/modules/ext/oracleappsadapter/wizard/
This package contains the VALIDATE procedure which eventually invokes all the VALIDATE procedures for all the tables.
Replace <%%UTILITY_PACKAGE_SQL_FILE_NAME%%> with the correct path and file name for the utility package. This utility package file name must be sql/business_function_name/<%%MODULE_NAME%%>/ <%%ORACLE_INTERFACE_NAME%%>/sb_interfaceNameAbbreviation_utils_pkg.sql, this path is relative from <CAPS_Dir>/edesigner/userdir/modules/ext/oracleappsadapter/wizard/
This package contains the procedures to move, delete, and function count all interface tables and the OTD level.
Replace <%%CONCURRENT_MANAGER_FUNCTION_SQL_FILE_NAME%%> with the correct path and file name for the concurrent file. This concurrent manager file name must be sql/business_function_name/<%%MODULE_NAME%%>/ <%%ORACLE_INTERFACE_NAME%%>/fn_request_<%%ORACLE_INTERFACE_NAME%%>.sql relative from <CAPS_Dir>/edesigner/userdir/modules/ext/oracleappsadapter/wizard/
This function eventually invokes the concurrent manager.
Replace <%%INTERFACE_TABLE_NAME%%> with the correct interface table name. Create more entries as needed for each interface table, either in the same level or as a child. For example, in manufacturing, order import has two interface tables with child-parent relationships, where as item import has two interface tables with sibling relationships.
Replace <%%INTERFACE_TABLE_VALIDATION_PACKAGE_SQL_FILE_NAME%%> with the correct path and file name for the validation package for this particular interface table. This validation package file name must be sql/business_function_name/<%%MDULE_NAME%%>/<%%ORACLE_INTERFACE_NAME%%>/sb_validate_interface_TablenameAbbreviation_pkg.sql
This path is relative from <CAPS_Dir>/edesigner/userdir/modules/ext/oracleappsadapter/wizard/.
This package has the VALIDATE procedure for these interface tables.
Restart the Java CAPS IDE so the OTD Wizard can load the new changes.
Create and compile the SQL scripts defined in the XML definition files. When creating SQL files, make sure that they begin with CREATE AND REPLACE.
The new Applications.xml, moduleDefinition.xml, and SQL scripts are stored only in the Java CAPS IDE directory. It is recommended to back them up periodically.
The default SQL script template for Concurrent Manager Request has 100 identical input parameters for FND_REQUEST.SUBMIT_REQUEST. If you need to customize the input parameters for your generated script, the following tags can be used to specify the input parameters.
<Concurrent_Manager>path/file_name.sql</Concurrent_Manager> <Request_Param>parameter1</Request_Param> <Request_Param>parameter2</Request_Param> <Request_Param>parameter3</Request_Param> |
The Data Type Definition (DTD) associated with the template XML file is shown:
<!ELEMENT OPEN_INTERFACE (Initialize_Script?, Validation_Script?, Utility_Script, Concurrent_Manager, Request_Param*, Concurrent_Manager_Status?, Interface_Table+, Error_Handle?, Pre_Required_Script*)> <!-- Open interface name --> <!ATTLIST OPEN_INTERFACE Name CDATA #REQUIRED > <!-- Oracle Manufacturing Version --> <!ATTLIST OPEN_INTERFACE Version CDATA #REQUIRED > <!-- Application Suite --> <!ATTLIST OPEN_INTERFACE Application-Suite CDATA #REQUIRED > <!-- Module Name --> <!ATTLIST OPEN_INTERFACE Module CDATA #REQUIRED > <!-- utiltiy store procedure name at root level, this attribute is optional if this attribute is specified, it overrides the default name convention, which is derived from Name attribute of OPEN_INTERFACE --> <!ATTLIST OPEN_INTERFACE Util_Name CDATA #IMPLIED > <!-- relative path to the sql script file for initialize package--> <!ELEMENT Initialize_Script (#PCDATA)> <!-- relative path to the sql script file for validation package --> <!ELEMENT Validation_Script (#PCDATA)> <!-- relative path to the sql script file for Utility package --> <!ELEMENT Utility_Script (#PCDATA)> <!-- relative path to the sql script file for concurrent manager request function --> <!ELEMENT Concurrent_Manager (#PCDATA)> <!-- parameter description for concurrent manager request function --> <!ELEMENT Request_Param (#PCDATA)> <!-- relative path to the sql script file for function to retrieve concurrent manager request status --> <!ELEMENT Concurrent_Manager_Status (#PCDATA)> <!-- Oracle Open Interface table definition --> <!ELEMENT Interface_Table (Validation_Script?, Interface_Table*)> <!-- name for the oracle open interface table --> <!ATTLIST Interface_Table Name CDATA #REQUIRED > <!-- name for SB staging table, this attribute is optional if this attribute is set, the program directly uses its value as the SB staging table for this specific interface --> <!ATTLIST Interface_Table SB_Name CDATA #IMPLIED > <!-- utility store procedure name at specific interface level, this attribute is optional if this attribute is specified, it overrides the default name convention, which is derived from the specific interface name --> <!ATTLIST Interface_Table Util_Name CDATA #IMPLIED > <!-- Error handling definition --> <!ELEMENT Error_Handle (Error_Table?, Error_PKG?)> <!-- relative path to the sql script for creating error table --> <!ELEMENT Error_Table (#PCDATA)> <!-- relative path to the sql script for error handling --> <!ELEMENT Error_PKG (#PCDATA)> <!-- relative path to the sql script that needs to be compiled in order for other stored procedure to be compiled successfully --> |
The specific name for the Open Interface, which is specified in the XML file.
The name used for the generated utility stored procedures, for each interface table. It is derived from the corresponding Oracle Interface Table name as follows:
If the Oracle Interface Table name is longer than 23 characters, replace INTERFACE or IFACE_ALL with INT to form the short table name.
(Since there is a limitation of 30 characters placed on the function/stored procedure name in Oracle, the Open Interface name specified in the XML file must be no more than 23 characters).
The utility stored procedure names are derived from the Short Table name, according to the following convention:
Sb_XXX_<SHORT_TABLE_NAME>
The name of the staging table node is derived from the corresponding Oracle Interface Table name by adding the prefix SB_ and truncating it to 30 characters, if necessary.
If the SQL file is used to create a packaged stored procedure, the file name must be the same as the package name. The file name is case sensitive and must be less than or equal to 30 character due to the rules of Oracle procedure/function name.
The function name is derived from the Open Interface name specified in the XML, and has the form: FN_REQUEST_<ORACLE_INTERFACE_NAME>.
The Manufacturing module is divided into the following sub-modules:
The Oracle Inventory module works with other Oracle Manufacturing modules to provide a complete set of transactions and reports for maintaining inventory control.
Oracle Interface Table — Oracle provides the following Interface Table for Customer Items: mtl_ci_interface
Sun Staging Table — The Oracle Applications Adapter sets up the following staging table, corresponding to the Oracle Open Interface Tables listed above: sb_mtl_ci_interface
Pre-Validation Script — The scripts corresponding to the Sun Staging Tables listed above are packaged within the following file: sb_validate_cust_items_pkg.sql
Oracle Interface Table — Oracle provides the following Interface Table for Customer Item Cross-References: mtl_ci_xrefs_interface
Sun Staging Table — The Oracle Applications Adapter sets up the following staging table, corresponding to the Oracle Open Interface Tables listed above:sb_mtl_ci_xrefs_interface
Pre-Validation Script — The scripts corresponding to the Sun Staging Tables listed above are packaged within the following file: sb_validate_ci_xrefs_pkg.sql
Oracle Interface Table — Oracle provides the following Interface Table for Cycle Count Entries: mtl_cc_entries_interface
Sun Staging Table— The Oracle Applications Adapter sets up the following staging table, corresponding to the Oracle Open Interface Table listed above: sb_mtl_cc_entries_interface
Pre-Validation Script— The scripts corresponding to the Sun Staging Table listed above are packaged within the following file: sb_validate_cc_entries_pkg.sql
Oracle Interface Tables— Oracle provides the following Interface Tables for items: mtl_system_items_interface and mtl_item_revisions_interface
Sun Staging Tables— The Oracle Applications Adapter sets up the following staging tables, corresponding to the Oracle Open Interface Tables listed above: sb_mtl_system_items_interface and
sb_mtl_item_revisions_int
Pre-Validation Scripts — The scripts corresponding to the Sun Staging Tables listed above are packaged within the following files: sb_validate_items_pkg.sql and sb_validate_invrev_pkg.sql
Oracle Interface Tables — Oracle provides the following Interface Tables for Item Replenishment: mtl_replenish_headers_int and mtl_replenish_lines_int
Sun Staging Tables — The Oracle Applications Adapter sets up the following staging tables, corresponding to the Oracle Open Interface Tables listed above: sb_mtl_replenish_headers_int and
sb_mtl_replenish_lines_int
Pre-Validation Scripts — The scripts corresponding to the Sun Staging Tables listed above are packaged within the following files: sb_validate_rep_headers_pkg.sql and sb_validate_rep_lines_pkg.sql
These files are controlled by the following master validation file:
sb_validate_rep_pkg.sql
Oracle Interface Tables — Oracle provides the following Interface Tables for Transactions:
mtl_transactions_interface
mtl_transaction_lots_interface
mtl_serial_numbers_interface
Sun Staging Tables — The Oracle Applications Adapter sets up the following staging tables, corresponding to the Oracle Open Interface Tables listed above:
sb_mtl_transactions_interface
sb_mtl_transaction_lots_inter
sb_mtl_serial_numbers_interface
Pre-Validation Scripts — The scripts corresponding to the Sun Staging Tables listed above are packaged within the following files:
sb_validate_trans_pkg.sql
sb_validate_trans_lots_pkg.sql
sb_validate_serial_nos_pkg.sql
These files are controlled by the following master validation file:
sb_validate_tran_all_pkg.sql
The Oracle Purchase Order Import module works with other Oracle Manufacturing modules to provide a complete set of transactions and reports for maintaining inventory control.
Oracle Interface Tables — Oracle provides the following Interface Tables for Purchase Order Import:
po_headers_interface
po_lines_interface
Sun Staging Tables — The Oracle Applications Adapter sets up the following staging tables, corresponding to the Oracle Open Interface Tables listed above:
Pre-Validation Scripts — The scripts corresponding to the Sun Staging Tables listed above are packaged within the following files:
sb_validate_poi_hdrs_pkg.sql
sb_validate_poi_lines_pkg.sql
These files are controlled by the following master validation file:
sb_validate_poi_pkg.sql
Oracle Interface Tables — Oracle provides the following Interface Tables for Receiving:
Sun Staging Tables — The Oracle Applications Adapter sets up the following staging tables, corresponding to the Oracle Open Interface Tables listed above:
Pre-Validation Scripts — The scripts corresponding to the Sun Staging Tables listed above are packaged within the following files:
sb_validate_rcv_hdr_pkg.sql
sb_validate_rcv_trans_pkg.sql
These files are controlled by the following master validation file:
sb_validate_rcv_pkg.sql
Oracle Interface Table — Oracle provides the following Interface Table for Requisitions: po_requisitions_interface_all
Sun Staging Table — The Oracle Applications Adapter sets up the following staging table, corresponding to the Oracle Open Interface Table listed above: sb_po_requisitions_interface_a
Pre-Validation Script — The scripts corresponding to the Sun Staging Table listed above are packaged within the following file: sb_validate_por_req_pkg.sql
The Oracle Order Entry module works with other Oracle Manufacturing modules to provide a complete set of transactions and reports for maintaining order entry control.
Oracle provides the following Interface Table for Order Entry:
oe_headers_interface
oe_lines_interface
oe_actions_interface
oe_credits_interface
oe_price_adjs_interface
oe_lotserials_interface
oe_reservtns_interface
sb_oe_headers_interface
sb_oe_lines_interface
sb_oe_actions_interface
sb_oe_credits_interface
sb_oe_price_adjs_interface
sb_oe_lotserials_interface
sb_oe_reservtns_interface
The scripts corresponding to the Sun Staging Tables listed above are packaged within the following file:
sb_validate_oe_pkg.sql
This file is controlled by the following master validation file:
sb_validate_oi_pkg.sql
The Financial module is divided into the following sub-modules:
The Oracle Accounts Payable module works with other Oracle Financial modules to provide a complete set of transactions and reports for maintaining accounts payable control.
Oracle Interface Tables — Oracle provides the following Interface Table for Requisitions:
ap_invoices_interface
ap_invoice_lines_interface
Sun Staging Tables — The Oracle Applications Adapter sets up the following staging table, corresponding to the Oracle Open Interface Table listed above:
sb_ap_invoices_interface
sb_ap_invoice_lines_interface
Pre-Validation Scripts — The scripts corresponding to the Sun Staging Tables listed above are packaged within the following files:
sb_validate_ap_inv_pkg.sql
sb_validate_ap_inv_lines_pkg.sql
These files are controlled by the following master validation file:
sb_validate_payable_pkg.sql
The Oracle Accounts Receivable module works with other Oracle Financial modules to provide a complete set of transactions and reports for maintaining accounts receivable control.
Oracle Interface Tables — Oracle provides the following Interface Table for Requisitions:
ra_interface_distributions
ra_interface_lines_all
ra_interface_salescredits_all
Sun Staging Tables — The Oracle Applications Adapter sets up the following staging table, corresponding to the Oracle Open Interface Table listed above:
sb_ra_interface_distributions
sb_ra_interface_lines_all
sb_ra_interface_salescredits_all
Pre-Validation Scripts — The scripts corresponding to the Sun Staging Tables listed above are packaged within the following files:
sb_validate_ra_dist_pkg.sql
sb_validate_ra_lines_pkg.sql
sb_validate_ra_sales_cr_pkg.sql
This file is controlled by the following master validation file:
sb_validate_auto_inv_pkg.sql
Oracle Interface Tables — Oracle provides the following Interface Table for Requisitions:
ar_payments_interface_all
Sun Staging Tables — The Oracle Applications Adapter sets up the following staging table, corresponding to the Oracle Open Interface Table listed above:
sb_ar_payments_interface_all
Pre-Validation Scripts — The scripts corresponding to the Sun Staging Tables listed above are packaged within the following file:
sb_validate_ar_payments_pkg.sql
This file is controlled by the following master validation file:
sb_validate_auto_lock_pkg.sql
Oracle Interface Tables — Oracle provides the following Interface Table for Requisitions:
ra_customers_interface
ra_contact_phones_int_all
ra_cust_pay_method_interface
ra_customer_banks_int_all
ra_customer_profiles_interface
Sun Staging Tables — The Oracle Applications Adapter sets up the following staging table, corresponding to the Oracle Open Interface Table listed above:
sb_ra_customers_interface
sb_ra_contact_phones_int_all
sb_ra_cust_pay_method_interface
sb_ra_customer_banks_int_all
sb_ra_customer_profiles_interface
Pre-Validation Scripts — The scripts corresponding to the Sun Staging Tables listed above are packaged within the following files:
sb_validate_cust_pkg.sql
sb_validate_contact_phones_pkg.sql
sb_validate_cust_pay_mtd_pkg.sql
sb_validate_cust_banks_pkg.sql
sb_validate_cust_profiles_pkg.sql
This file is controlled by the following master validation file:
sb_validate_customers_pkg.sql
The Oracle Cash Management module works with other Oracle Financial modules to provide a complete set of transactions and reports for maintaining cash management control.
Oracle Interface Tables — Oracle provides the following Interface Table for Requisitions:
ce_statement_headers_int_all
ce_statement_lines_interface
Sun Staging Tables — The Oracle Applications Adapter sets up the following staging table, corresponding to the Oracle Open Interface Table listed above:
sb_ce_statement_headers_int_all
sb_ce_statement_lines_interface
Pre-Validation Scripts — The scripts corresponding to the Sun Staging Tables listed above are packaged within the following files:
sb_validate_stmt_headers_pkg.sql
sb_validate_stmt_lines_pkg.sql
These files are controlled by the following master validation file:
sb_validate_bank_stmt_pkg.sql
The Oracle Fixed Assets module works with other Oracle Financial modules to provide a complete set of transactions and reports for maintaining fixed asset control.
Oracle Interface Tables — Oracle provides the following Interface Table for Requisitions:
fa_categories_b
Sun Staging Tables — The Oracle Applications Adapter sets up the following staging table, corresponding to the Oracle Open Interface Table listed above:
sb_fa_categories_b
Pre-Validation Scripts — The scripts corresponding to the Sun Staging Tables listed above are packaged within the following file:
sb_validate_cat_pkg.sql
This file is controlled by the following master validation file:
sb_validate_fa_categories_pkg.sql
Oracle Interface Tables — Oracle provides the following Interface Table for Requisitions:
fa_locations
Sun Staging Tables — The Oracle Applications Adapter sets up the following staging table, corresponding to the Oracle Open Interface Table listed above:
sb_fa_locations
Pre-Validation Scripts — The scripts corresponding to the Sun Staging Tables listed above are packaged within the following files:
sb_validate_loc_pkg.sql
These files are controlled by the following master validation file:
sb_validate_fa_locations_pkg.sql
Oracle Interface Tables — Oracle provides the following Interface Table for Requisitions:
fa_mass_additions
Sun Staging Tables — The Oracle Applications Adapter sets up the following staging table, corresponding to the Oracle Open Interface Table listed above:
sb_fa_mass_additions
Pre-Validation Scripts — The scripts corresponding to the Sun Staging Tables listed above are packaged within the following files:
sb_validate_additions_pkg.sql
These files are controlled by the following master validation file:
sb_validate_fa_mass_add_pkg.sql
The Oracle General Ledger module works with other Oracle Financial modules to provide a complete set of transactions and reports for maintaining general ledger control.
Oracle Interface Tables — Oracle provides the following Interface Table for Requisitions:
gl_budget_interface
Sun Staging Tables — The Oracle Applications Adapter sets up the following staging table, corresponding to the Oracle Open Interface Table listed above:
sb_gl_budget_interface
Pre-Validation Scripts — The scripts corresponding to the Sun Staging Tables listed above are packaged within the following files:
sb_validate_gl_budget_pkg.sql
These files are controlled by the following master validation file:
sb_validate_budget_pkg.sql
Oracle Interface Tables — Oracle provides the following Interface Table for Requisitions:
gl_daily_rates_interface
Sun Staging Tables — The Oracle Applications Adapter sets up the following staging table, corresponding to the Oracle Open Interface Table listed above:
sb_gl_daily_rates_interface
Pre-Validation Scripts — The scripts corresponding to the Sun Staging Tables listed above are packaged within the following files:
sb_validate_gl_daily_rates_pkg.sql
These files are controlled by the following master validation file:
sb_validate_dailyrates_pkg.sql
Oracle Interface Tables — Oracle provides the following Interface Table for Requisitions:
gl_interface
Sun Staging Tables — The Oracle Applications Adapter sets up the following staging table, corresponding to the Oracle Open Interface Table listed above:
sb_gl_interface
Oracle Applications Adapter — The scripts corresponding to the Sun Staging Tables listed above are packaged within the following files:
sb_validate_gl_int_pkg.sql
These files are controlled by the following master validation file:
sb_validate_journal_pkg.sql
This section provides a description of each of the following error code types returned by the validation scripts:
If new Error Codes are needed, you must drop the current sb_errors table and either manually or automatically (through the OTD builder) re-run the sb_install.sql script so that a new sb_errors table is created with new entries.hi.
A description of the validation process is found in Building an Oracle Applications Custom Pre-Validation Package.
This section provides a description of each of the following Manufacturing error codes:
This section provides a description of each of the Inventory error codes.
The Customer Items are listed in the table.
Table 1–2 Customer Item Errors
Error Code |
Error Message |
---|---|
SB-INVCIT-25301 |
Customer_Item_Number is mandatory and the current value is NULL. |
SB-INVCIT-25302 |
Transaction_Type is mandatory and the current value is NULL. |
SB-INVCIT-25303 |
Item_Definition_Level is mandatory and the current value is NULL. |
SB-INVCIT-25304 |
Customer ID, Number and Name are mandatory and the current value is NULL. |
SB-INVCIT-25305 |
Address columns are mandatory and the current value is NULL. |
SB-INVCIT-25306 |
Customer category columns are mandatory and the current value is NULL. |
SB-INVCIT-25307 |
Commodity code columns are mandatory and the current value is NULL. |
SB-INVCIT-25308 |
Container item org columns are mandatory and the current value is NULL. |
SB-INVCIT-25309 |
Model customer item columns are mandatory and the current value is NULL. |
SB-INVCIT-25310 |
Customer_ID is invalid. |
SB-INVCIT-25311 |
Customer_Number is invalid. |
SB-INVCIT-25312 |
Customer_Name is invalid. |
SB-INVCIT-25313 |
Address_ID is invalid. |
SB-INVCIT-25314 |
Customer Category columns are invalid. |
SB-INVCIT-25315 |
Model customer item columns are invalid. |
SB-INVCIT-25316 |
Commodity code is inactive. |
SB-INVCIT-25317 |
Constainer_item_org_id is invalid. |
SB-INVCIT-25318 |
Inactive flag has invalid value. |
SB-INVCIT-25319 |
Container_org_code is invalid. |
SB-INVCIT-25320 |
Container org name is invalid. |
SB-INVCIT-25321 |
Demand tolerance positive value is invalid. |
SB-INVCIT-25322 |
Demand tolerance negative value is invalid. |
SB-INVCIT-25323 |
Min_Fill_Percentage is invalid. |
SB-INVCIT-25324 |
Departure plan required flag is invalid. |
SB-INVCIT-25325 |
Departure plan build flag is invalid. |
SB-INVCIT-25326 |
Departure plan flags combination is invalid. |
The Customer Item Cross-Reference is listed in the table.
Table 1–3 Customer Item Cross-Reference Errors
Error Code |
Error Message |
---|---|
SB-INVCCR-22601 |
Process_flag is mandatory and the current value is NULL. |
SB-INVCCR-22602 |
Process_mode is mandatory and the current value is NULL. |
SB-INVCCR-22603 |
Last_update_date is mandatory and the current value is NULL. |
SB-INVCCR-22604 |
Last_updated_by is mandatory and the current value is NULL. |
SB-INVCCR-22605 |
Creation_date is mandatory and the current value is NULL. |
SB-INVCCR-22606 |
Created_by is mandatory and the current value is NULL. |
SB-INVCCR-22607 |
Transaction_Type is mandatory and the current value is NULL. |
SB-INVCCR-22608 |
Cust_Item_Number is mandatory and the current value is NULL. |
SB-INVCCR-22609 |
Preference_Number is mandatory and the current value is NULL. |
SB-INVCCR-22610 |
Inactive_flag is mandatory and the current value is NULL. |
SB-INVCCR-22611 |
Lock_flag is mandatory and the current value is NULL. |
SB-INVCCR-22612 |
Cust_Category is mandatory and the current value is NULL. |
SB-INVCCR-22613 |
Address is mandatory and the current value is NULL. |
SB-INVCCR-22614 |
Item_Def_Level is mandatory and the current value is NULL. |
SB-INVCCR-22615 |
Customer is mandatory and the current value is NULL. |
SB-INVCCR-22616 |
Customer_ID is invalid. |
SB-INVCCR-22617 |
Customer_No is invalid. |
SB-INVCCR-22618 |
Customer_Name is invalid. |
SB-INVCCR-22619 |
Address_Valid is invalid. |
SB-INVCCR-22620 |
Cust_Cat_Code is invalid. |
SB-INVCCR-22621 |
Customer_item_id is invalid. |
SB-INVCCR-22622 |
Master_Organization_id is invalid. |
SB-INVCCR-22623 |
Inventory_Item_id is invalid. |
SB-INVCCR-22624 |
Inactive_Flag is invalid. |
The Cycle Count Entries are listed in the table.
Table 1–4 Cycle Count Entry Errors
Error Code |
Error Message |
---|---|
SB-INVCCE-23301 |
CC_ENTRY_INTERFACE_ID is mandatory and the current value is NULL. |
SB-INVCCE-23302 |
ORGANIZATION_ID is mandatory and the current value is NULL. |
SB-INVCCE-23303 |
ACTION_CODE is mandatory and the current value is NULL. |
SB-INVCCE-23304 |
EMPLOYEE_ID is mandatory and the current value is NULL. |
SB-INVCCE-23310 |
ADJUSTMENT_ACCOUNT_ID is invalid. |
SB-INVCCE-23311 |
CYCLE_COUNT_ENTRY_ID is invalid. |
SB-INVCCE-23312 |
CYCLE_COUNT_HEADER_ID is invalid. |
SB-INVCCE-23313 |
LOCATOR_ID is invalid. |
SB-INVCCE-23314 |
REVISION is invalid. |
SB-INVCCE-23315 |
LOT_NUMBER is invalid. |
SB-INVCCE-23316 |
ORGANIZATION_ID is invalid. |
SB-INVCCE-23317 |
SUBINVENTORY is invalid. |
SB-INVCCE-23318 |
SERIAL_NUMBER is invalid. |
SB-INVCCE-23319 |
INVENTORY_ITEM_ID is invalid. |
SB-INVCCE-23320 |
TRANSACTION_REASON_ID is invalid. |
SB-INVCCE-23321 |
COUNT_UNIT_OF_MEASURE is invalid. |
SB-INVCCE-23322 |
COUNT_UOM is invalid. |
SB-INVCCE-23330 |
EMPLOYEE_ID value is not valid. |
SB-INVCCE-23331 |
PROJECT_ID value is not valid. |
SB-INVCCE-23332 |
TASK_ID value is not valid. |
SB-INVCCE-23333 |
VALID_FLAG value is not valid. |
SB-INVCCE-23334 |
DELETE_FLAG value is not valid. |
SB-INVCCE-23335 |
LOCK_FLAG value is not valid. |
SB-INVCCE-23336 |
PROCESS_FLAG value is not valid. |
SB-INVCCE-23337 |
PROCESS_MODE value is not valid. |
SB-INVCCE-23338 |
STATUS_FLAG value is not valid. |
The Item Entries are listed in the table.
Table 1–5 Item Errors
Error Code |
Error Message |
---|---|
SB-INVITM-21301 |
Organization_Code or Organization_ID is mandatory and the current value is NULL. |
SB-INVITM-21302 |
item_Number or Segment#s 1 to 20 is mandatory and the current value is NULL. |
SB-INVITM-21303 |
Process_Flag is mandatory and the current value is NULL. |
SB-INVITM-21304 |
Transaction_Type is mandatory and the current value is NULL. |
SB-INVITM-21305 |
Set_Process_ID is mandatory and the current value is NULL. |
SB-INVITM-21306 |
Summary_Flag is invalid. |
SB-INVITM-21307 |
Enabled_Flag is invalid. |
SB-INVITM-21308 |
Purchasing_Item_Flag is invalid. |
SB-INVITM-21309 |
Shippable_Item_Flag is invalid. |
SB-INVITM-21310 |
Customer_Order_Flag is invalid. |
SB-INVITM-21311 |
Internal_Order_Flag is invalid. |
SB-INVITM-21312 |
Service_Item_Flag is invalid. |
SB-INVITM-21313 |
Service_Starting_Delay is less than Zero. |
SB-INVITM-21314 |
Inventory_Item_Flag is invalid. |
SB-INVITM-21315 |
Eng_Item_Flag is invalid. |
SB-INVITM-21316 |
Inventory_Asset_Flag is invalid. |
SB-INVITM-21317 |
Purchasing_Enabled_Flag is invalid. |
SB-INVITM-21318 |
Customer_Order_Enabled_Flag is invalid. |
SB-INVITM-21319 |
Internal_Order_Enabled_Flag is invalid. |
SB-INVITM-21320 |
So_Transactions_Flag is invalid. |
SB-INVITM-21321 |
Mtl_Transactions_Enabled_Flag is invalid. |
SB-INVITM-21322 |
Stock_Enabled_Flag is invalid. |
SB-INVITM-21323 |
Bom_Enabled_Flag is invalid. |
SB-INVITM-21324 |
Build_In_Wip_Flag is invalid. |
SB-INVITM-21325 |
Allow_Item_Desc_Update_Flag is invalid. |
SB-INVITM-21326 |
Receipt_Required_Flag is invalid. |
SB-INVITM-21327 |
Rfq_Required_Flag is invalid. |
SB-INVITM-21328 |
Planning_Time_Fence_Days is less than Zero. |
SB-INVITM-21329 |
Pick_Components_Flag is invalid. |
SB-INVITM-21330 |
Replenish_To_Order_Flag is invalid. |
SB-INVITM-21331 |
ATP_Components_Flag is invalid. |
SB-INVITM-21332 |
Cost_Of_Sales_Account is invalid. |
SB-INVITM-21333 |
Sales_Account is invalid. |
SB-INVITM-21334 |
Encumbrance_Account is invalid. |
SB-INVITM-21335 |
Expense_Account is invalid. |
SB-INVITM-21336 |
List_Price_Per_Unit is less than Zero. |
SB-INVITM-21337 |
Taxable_Flag is invalid. |
SB-INVITM-21338 |
Expense_Billable_Flag is invalid. |
SB-INVITM-21339 |
Time_Billable_Flag is invalid. |
SB-INVITM-21340 |
Service_Duration is invalid. |
SB-INVITM-21341 |
Market_Price is less than Zero. |
SB-INVITM-21342 |
Price_Tolerance_Percent is less than Zero. |
SB-INVITM-21343 |
Shelf_Life_Days is less than Zero. |
SB-INVITM-21344 |
Repetitive_Planning_Flag is invalid. |
SB-INVITM-21345 |
Acceptable_Rate_Decrease is less than Zero. |
SB-INVITM-21346 |
Acceptable_Rate_Increase is less than Zero. |
SB-INVITM-21347 |
Assembly_Pegging_Flag is invalid. |
SB-INVITM-21348 |
Postprocessing_Lead_Time is less than Zero. |
SB-INVITM-21349 |
Vendor_Warranty_Flag is invalid. |
SB-INVITM-21350 |
Serviceable_Component_Flag is invalid. |
SB-INVITM-21351 |
Serviceable_Product_Flag is invalid. |
SB-INVITM-21352 |
Preventive_Maintenance_Flag is invalid. |
SB-INVITM-21353 |
Ship_Model_Complete_Flag is invalid. |
SB-INVITM-21354 |
Prorate_Service_Flag is invalid. |
SB-INVITM-21355 |
Invoiceable_Item_Flag is invalid. |
SB-INVITM-21356 |
Invoice_Enabled_Flag is invalid. |
SB-INVITM-21357 |
Must_Use_Approved_Vendor_Flag is invalid. |
SB-INVITM-21358 |
Outside_Operation_Flag is invalid. |
SB-INVITM-21359 |
Costing_Enabled_Flag is invalid. |
SB-INVITM-21360 |
Cycle_Count_Enabled_Flag is invalid. |
SB-INVITM-21361 |
Auto_Created_Config_Flag is invalid. |
SB-INVITM-21362 |
Container_Item_Flag is invalid. |
SB-INVITM-21363 |
Vehicle_Item_Flag is invalid. |
SB-INVITM-21364 |
Check_Org_ID_Code is invalid. |
SB-INVITM-21365 |
Wip_Supply_Type is invalid. |
SB-INVITM-21366 |
Lot_Control_Code is invalid. |
SB-INVITM-21367 |
Shelf_Life_Code is invalid. |
SB-INVITM-21368 |
Serial_Number_Control_Code is invalid. |
SB-INVITM-21369 |
Restrict_Subinventories_Code is invalid. |
SB-INVITM-21370 |
Restrict_Locators_Code is invalid. |
SB-INVITM-21371 |
Planning_Time_Fence_Code is invalid. |
SB-INVITM-21372 |
Bom_Item_Type is invalid. |
SB-INVITM-21373 |
Allowed_Units_Lookup_Code is invalid. |
SB-INVITM-21374 |
Inventory_Planning_Code is invalid. |
SB-INVITM-21375 |
Planning_Make_Buy_Code is invalid. |
SB-INVITM-21376 |
Mrp_Safety_Stock_Code is invalid. |
SB-INVITM-21377 |
Material_Billable_Flag is invalid. |
SB-INVITM-21378 |
Reservable_Type is invalid. |
SB-INVITM-21379 |
Return_Inspection_Requirement is invalid. |
SB-INVITM-21380 |
Mrp_Planning_Code is invalid. |
SB-INVITM-21381 |
Location_Control_Code is invalid. |
SB-INVITM-21382 |
ITEM DESCRIPTION FIELD CANNOT BE NULL. |
The Item Revisions are listed in the table.
Table 1–6 Item Revision Errors
Error Code |
Error Message |
---|---|
SB-INVREV-22500 |
Set_process_ID is mandatory and the current value is NULL. |
SB-INVREV-22501 |
Inventory_Item_ID is mandatory and the current value is NULL. |
SB-INVREV-22502 |
Organization_ID is mandatory and the current value is NULL. |
SB-INVREV-22503 |
Revision is mandatory and the current value is NULL. |
SB-INVREV-22504 |
Change_Notice is invalid. |
SB-INVREV-22505 |
Organization_id is invalid. |
SB-INVREV-22506 |
Inventory_item_id is invalid. |
SB-INVREV-22507 |
Primary_key is invalid. |
SB-INVREV-22508 |
Process_flag is invalid. |
SB-INVREV-22509 |
Item_Number is invalid. |
Master
The Replenishment Master Errors are listed in the table.
Table 1–7 Replenishment Master Errors
Error Code |
Error Message |
---|---|
SB-INVREP-22430 |
Header has lines that have failed validation. |
Headers
The Replenishment Header Errors are listed in the table.
Table 1–8 Replenishment Header Errors
Error Code |
Error Message |
---|---|
SB-INVREP-22301 |
Replenishment_Header_ID is mandatory and the current value is NULL. |
SB-INVREP-22302 |
Replenishment_Count_Name is mandatory and the current value is NULL. |
SB-INVREP-22303 |
Count_Date is mandatory and the current value is NULL. |
SB-INVREP-22304 |
Last_Update_Date is mandatory and the current value is NULL. |
SB-INVREP-22305 |
Creation_Date is mandatory and the current value is NULL. |
SB-INVREP-22306 |
Created_By is mandatory and the current value is NULL. |
SB-INVREP-22307 |
Last_Updated_By is mandatory and the current value is NULL. |
SB-INVREP-22308 |
Organization_ID is mandatory and the current value is NULL. |
SB-INVREP-22309 |
SubInventory_Code is mandatory and the current value is NULL. |
SB-INVREP-22310 |
Process_Status is mandatory and the current value is NULL. |
SB-INVREP-22311 |
Process_Mode is mandatory and the current value is NULL. |
SB-INVREP-22312 |
Organization_ID is invalid. |
SB-INVREP-22313 |
SubInventory_Code is invalid. |
SB-INVREP-22314 |
Error_Flag is invalid. |
SB-INVREP-22315 |
Process_Mode is invalid. |
SB-INVREP-22316 |
Process_Status is invalid. |
SB-INVREP-22317 |
Replenish_Header is invalid. |
SB-INVREP-22318 |
Replenish_Count is invalid. |
SB-INVREP-22319 |
Last_Update is invalid. |
SB-INVREP-22320 |
Lines is invalid. |
Lines
The Replenishment Line Errors are listed in the table.
Table 1–9 Replenishment Line Errors
Error Code |
Error Message |
---|---|
SB-INVREP-22401 |
Replenishment_Header_ID is mandatory and the current value is NULL |
SB-INVREP-22402 |
Replenishment_Line_ID is mandatory and the current value is NULL |
SB-INVREP-22403 |
Last_Update_Date is mandatory and the current value is NULL |
SB-INVREP-22404 |
Creation_Date is mandatory and the current value is NULL |
SB-INVREP-22405 |
Created_By is mandatory and the current value is NULL |
SB-INVREP-22406 |
Last_Update_Login is mandatory and the current value is NULL |
SB-INVREP-22407 |
Last_Updated_By is mandatory and the current value is NULL |
SB-INVREP-22408 |
Inventory_Item_ID is mandatory and the current value is NULL |
SB-INVREP-22409 |
Count_Type_Code is mandatory and the current value is NULL |
SB-INVREP-22410 |
Count_Quantity is mandatory and the current value is NULL |
SB-INVREP-22411 |
Count_UOM is mandatory and the current value is NULL |
SB-INVREP-22412 |
Count_UOM_Code is mandatory and the current value is NULL |
SB-INVREP-22413 |
Organization_ID is invalid. |
SB-INVREP-22414 |
Rep_Header_ID is invalid. |
SB-INVREP-22415 |
Inventory_Item_ID is invalid. |
SB-INVREP-22416 |
Count_Uom is invalid. |
SB-INVREP-22417 |
Count_Uom_Code is invalid. |
SB-INVREP-22418 |
Segment is invalid. |
SB-INVREP-22419 |
Count_Type_Code is invalid. |
SB-INVREP-22420 |
Organization_ID is invalid. |
SB-INVREP-22421 |
Count_Type_Tracked is invalid. |
SB-INVREP-22421 |
Count_Type_Tracked23 is invalid. |
SB-INVREP-22422 |
Inventory_item is invalid. |
SB-INVREP-22423 |
MinMAx_Plan is invalid. |
SB-INVREP-22424 |
Count_Uom_Primary is invalid. |
Transactions
The Transaction Errors are listed in the table.
Table 1–10 Transaction Errors
Error Code |
Error Message |
---|---|
SB-INVTXN-20301 |
Source Code is mandatory and the current value is NULL. |
SB-INVTXN-20302 |
Source Line ID is mandatory and the current value is NULL. |
SB-INVTXN-20303 |
Source Header ID is mandatory and the current value is NULL. |
SB-INVTXN-20304 |
Process Flag is mandatory and the current value is NULL. |
SB-INVTXN-20305 |
Transaction Mode is mandatory and the current value is NULL. |
SB-INVTXN-20306 |
Transaction Interface ID is mandatory and the current value is NULL. |
SB-INVTXN-20307 |
Inventory Item ID is mandatory and the current value is NULL. |
SB-INVTXN-20308 |
Organization ID is mandatory and the current value is NULL. |
SB-INVTXN-20309 |
Transaction Quantity is mandatory and the current value is NULL. |
SB-INVTXN-20310 |
Transaction UOM is mandatory and the current value is NULL. |
SB-INVTXN-20311 |
Transaction Date is mandatory and the current value is NULL. |
SB-INVTXN-20312 |
Transaction Source ID is mandatory and the current value is NULL. |
SB-INVTXN-20313 |
Transaction Source Name is mandatory and the current value is NULL. |
SB-INVTXN-20314 |
Transaction Type ID is mandatory and the current value is NULL. |
SB-INVTXN-20319 |
Distribution Account ID is invalid. |
SB-INVTXN-20320 |
Inventory Item ID is invalid. |
SB-INVTXN-20321 |
Organization ID is invalid. |
SB-INVTXN-20322 |
Acct Period ID is invalid. |
SB-INVTXN-20323 |
Schedule ID is invalid. |
SB-INVTXN-20324 |
Operation Seq Num is invalid. |
SB-INVTXN-20325 |
Transportation Account is invalid. |
SB-INVTXN-20326 |
Locator ID is invalid. |
SB-INVTXN-20327 |
Transfer Organization is invalid. |
SB-INVTXN-20328 |
Transfer Locator is invalid. |
SB-INVTXN-20329 |
Revision is invalid. |
SB-INVTXN-20330 |
SubInventory Code is invalid. |
SB-INVTXN-20331 |
Transfer SubInventory is invalid. |
SB-INVTXN-20332 |
Schedule Number is invalid. |
SB-INVTXN-20333 |
Reason ID is invalid. |
SB-INVTXN-20334 |
Wip Entity Type is invalid. |
SB-INVTXN-20335 |
Substitution Type ID is invalid. |
SB-INVTXN-20344 |
Transaction Header ID is invalid. |
Lots
The Transaction Lots Errors are listed in the table.
Table 1–11 Transaction Lots Errors
Error Code |
Error Message |
---|---|
SB-INVTXN-20336 |
Transaction Interface ID is mandatory and the current value is NULL. |
SB-INVTXN-20337 |
Lot Number is mandatory and the current value is NULL. |
SB-INVTXN-20338 |
Transaction Quantity is mandatory and the current value is NULL. |
SB-INVTXN-20339 |
Transaction Temp ID is invalid. |
SB-INVTXN-20340 |
Transaction Interface ID is invalid. |
Serial Numbers
The Transaction Serial Number Errors are listed in the table.
Table 1–12 Transaction Serial Number Errors
Error Code |
Error Message |
---|---|
SB-INVTXN-20341 |
Transaction Interface ID is mandatory and the current value is NULL. |
SB-INVTXN-20342 |
Fm Serial Number is mandatory and the current value is NULL. |
SB-INVTXN-20343 |
Vendor Serial Number is invalid. |
This section provides a description of each of the Purchase Order error codes.
Master
The Import Master Errors are listed in the table.
Table 1–13 Import Master Errors
Error Code |
Error Message |
---|---|
SB-POIMP-20001 |
Header record does not exist for Po_Header_ID. |
SB-POIMP-25006 |
Header has lines that have failed validation. |
Headers
The Import Header Errors are listed in the table.
Table 1–14 Import Header Errors
Error Code |
Error Message |
---|---|
SB-POIMP-20002 |
Interface Header ID is mandatory and the current value is NULL. |
SB-POIMP-20003 |
Action is mandatory and the current value is NULL. |
SB-POIMP-20004 |
Document Type Code is mandatory and the current value is NULL. |
SB-POIMP-20006 |
Vendor Site Code is mandatory and the current value is NULL. |
SB-POIMP-20007 |
Vendor Doc Num is mandatory and the current value is NULL. |
SB-POIMP-20008 |
Action is mandatory and the current value is invalid. |
SB-POIMP-20009 |
Document Type Code is mandatory and the current value is invalid. |
SB-POIMP-20010 |
Vendor ID is invalid. |
SB-POIMP-20011 |
From Type Lookup Code is invalid. |
SB-POIMP-20012 |
Ship To Location ID is invalid. |
SB-POIMP-20013 |
Terms ID is invalid. |
SB-POIMP-20014 |
Ussgl Transaction Code is invalid. |
SB-POIMP-20015 |
Buyer specified is invalid. |
SB-POIMP-20016 |
Bill To Location ID is invalid. |
SB-POIMP-20017 |
Vendor Site ID is invalid. |
SB-POIMP-20018 |
Vendor Contact ID is invalid. |
SB-POIMP-20019 |
From Header ID is invalid. |
SB-POIMP-20020 |
Rate Type is invalid. |
SB-POIMP-20021 |
Currency Code is invalid. |
SB-POIMP-20022 |
Document Number is invalid. |
SB-POIMP-20023 |
Buyer Name is invalid. |
SB-POIMP-20024 |
Vendor Name or Vendor Num is invalid. |
SB-POIMP-20025 |
Vendor Site Code is invalid. |
SB-POIMP-20026 |
Vendor Contact is invalid. |
SB-POIMP-20027 |
Ship To Location Code is invalid. |
SB-POIMP-20028 |
Bill To Location Code is invalid. |
SB-POIMP-20029 |
Payment Terms is invalid. |
SB-POIMP-20030 |
Rfq Num is invalid. |
SB-POIMP-20031 |
Amount Limit is less than Amount Agreed. |
SB-POIMP-20032 |
Amount Limit is less than Min Release Amount. |
SB-POIMP-20033 |
Amount Limit is less than Zero. |
SB-POIMP-20088 |
Release Number is invalid. |
SB-POIMP-25007 |
Document Type is Standard, so Action cannot be Update or Replace. |
SB-POIMP-25008 |
Document Type is Standard, so Approval Status must be Incomplete. |
SB-POIMP-25009 |
Vendor Doc Num does not exist. |
SB-POIMP-25010 |
Vendor Doc Num already exists. |
SB-POIMP-25011 |
Release Date is reserved for future use and must be NULL. |
SB-POIMP-25012 |
Document Num must have a unique value, Current value already exists. |
SB-POIMP-25013 |
There must be at least one line per header document. |
SB-POIMP-25014 |
Fob_Active is invalid. |
SB-POIMP-25015 |
Freight_Terms_Active is invalid. |
SB-POIMP-25016 |
Document_Sub_Type is invalid. |
SB-POIMP-25017 |
Num_Of_Lines is invalid. |
Lines
The Import Line Errors are listed in the table.
Table 1–15 Import Line Errors
Error Code |
Error Message |
---|---|
SB-POIMP-20034 |
Interface Header ID is mandatory and the current value is NULL. |
SB-POIMP-20035 |
Interface Line ID is mandatory and the current value is NULL. |
SB-POIMP-20036 |
Organization ID is mandatory and the current value is NULL. |
SB-POIMP-20037 |
Po Header ID not found for modification. |
SB-POIMP-20038 |
Category ID is invalid. |
SB-POIMP-20039 |
Line Type ID is invalid. |
SB-POIMP-20040 |
Un Number ID is invalid. |
SB-POIMP-20041 |
Hazard Class ID is invalid. |
SB-POIMP-20042 |
Ussgl Transaction Code is invalid. |
SB-POIMP-20043 |
Closed By is invalid. |
SB-POIMP-20044 |
From Header ID is invalid. |
SB-POIMP-20045 |
From Line ID is invalid. |
SB-POIMP-20046 |
Tax Name is invalid. |
SB-POIMP-20047 |
Item Revision is invalid. |
SB-POIMP-20048 |
Unit Of Measure is invalid. |
SB-POIMP-20049 |
Unit Of Measure is invalid for the Item ID/Organization ID. |
SB-POIMP-20050 |
Item ID is invalid. |
SB-POIMP-20052 |
Item is invalid. |
SB-POIMP-20054 |
Uom Code is invalid. |
SB-POIMP-20055 |
Line Type is invalid. |
SB-POIMP-20056 |
Line Num is invalid. |
SB-POIMP-20057 |
Shipment Num is invalid. |
SB-POIMP-20058 |
Un Number is invalid. |
SB-POIMP-20059 |
Hazard Class is invalid. |
SB-POIMP-20060 |
Ship To Organization Code is invalid. |
SB-POIMP-20061 |
Ship To Location Code is invalid. |
SB-POIMP-20062 |
Template Name is invalid. |
SB-POIMP-20063 |
Payment Terms is invalid. |
SB-POIMP-20064 |
Receiving Routing is invalid. |
SB-POIMP-20065 |
Tax Code ID is invalid. |
SB-POIMP-20066 |
Not To Exceed Price must be NULL since Allow Price Override Flag is N. |
SB-POIMP-20067 |
Not To Exceed Price has to be greater or equal to Unit Price. |
SB-POIMP-20068 |
Max Order Quantity must be greater than Min Order Quantity. |
SB-POIMP-20069 |
Closed Code must be null for QUOTATION Document Type. |
SB-POIMP-20070 |
Committed Amount must be null for QUOTATION Document Type. |
SB-POIMP-20071 |
Market Price must be null for QUOTATION Document Type. |
SB-POIMP-20072 |
Allow Price Override Flag must be null for QUOTATION Document Type. |
SB-POIMP-20073 |
Not To Exceed Price must be null for QUOTATION Document Type. |
SB-POIMP-20074 |
Negotiated By Preparer Flag must be null for QUOTATION Document Type. |
SB-POIMP-20075 |
Capital Expense Flag must be null for QUOTATION Document Type. |
SB-POIMP-20076 |
Min Release Amount for QUOTATION/BLANKET Document Type. |
SB-POIMP-20077 |
Min Order Quantity is less than 0. |
SB-POIMP-20078 |
Max Order Quantity is less than 0. |
SB-POIMP-20079 |
Over Tolerance Error Flag must be either Y or N. |
SB-POIMP-20080 |
Qty Rcv Tolerance must be NULL for BLANKET Document Type. |
SB-POIMP-20081 |
Qty Rcv Exception Code must be NULL for BLANKET Document Type. |
SB-POIMP-20082 |
Freight Carrier must be NULL for BLANKET Document Type. |
SB-POIMP-20083 |
Fob must be NULL for BLANKET Document Type. |
SB-POIMP-20084 |
Freight Terms must be NULL for BLANKET Document Type. |
SB-POIMP-20085 |
Receipt Required Flag must be NULL for BLANKET Document Type. |
SB-POIMP-20086 |
Inspection Required Flag must be NULL for BLANKET Document Type. |
SB-POIMP-20087 |
Unit Price must not be NULL or < 0. |
SB-POIMP-20088 |
Release Num is reserved for future use and must be NULL. |
SB-POIMP-20089 |
Po Release ID is reserved for future use and must be NULL. |
SB-POIMP-20090 |
Source Shipment ID is reserved for future use and must be NULL. |
SB-POIMP-20091 |
Contract Num is reserved for future use and must be NULL. |
SB-POIMP-20092 |
Type 1099 must be NULL. |
SB-POIMP-20093 |
Receipt Days Exception Code must be NULL. |
SB-POIMP-20094 |
Need By Date must be NULL. |
SB-POIMP-20095 |
Promised Date must be NULL. |
SB-POIMP-20096 |
Closed Reason must be NULL. |
SB-POIMP-20097 |
Closed Date must be NULL. |
SB-POIMP-20098 |
Closed By must be NULL. |
SB-POIMP-20099 |
Firm Flag must be NULL. |
SB-POIMP-20100 |
Quantity must be greater than 0. |
SB-POIMP-25001 |
Committed Amount must be greater than 0. |
SB-POIMP-25002 |
Market Price must be greater than 0. |
SB-POIMP-25003 |
Negotiated By Preparer Flag must be either Y or N. |
SB-POIMP-25004 |
Capital Expense Flag must be either Y or N. |
SB-POIMP-25005 |
Tax name and Tax Code ID must be NULL if Taxable Flag is NULL or N. |
SB-POIMP-25014 |
FOB is inactive. |
SB-POIMP-25015 |
Freight_Terms is inactive. |
Master
The Receiving Master Errors are listed in the table.
Table 1–16 Receiving Master Errors
Error Code |
Error Message |
---|---|
SB-POREC-25006 |
Header has lines that have failed validation. |
Headers
The Receiving Header Errors are listed in the table.
Table 1–17 Receiving Header Errors
Error Code |
Error Message |
---|---|
SB-POREC-20100 |
Header_Interface_ID field is mandatory in RCV_HEADERS_INTERFACE table and current value is null. |
SB-POREC-20101 |
Group_ID field is mandatory in RCV_HEADERS_INTERFACE table and current value is null. |
SB-POREC-20102 |
Processing_Status_Code field is mandatory in RCV_HEADERS_INTERFACE table and current value is null. |
SB-POREC-20103 |
Receipt_Source_Code field is mandatory in RCV_HEADERS_INTERFACE table and current value is null. |
SB-POREC-20104 |
Transaction_Type field is mandatory in RCV_HEADERS_INTERFACE table and current value is null. |
SB-POREC-20105 |
Value Required in Vendor_Name or Vendor_Num field in RCV_HEADERS_INTERFACE table and current value is null. |
SB-POREC-20106 |
Validation_Flag is mandatory in RCV_HEADERS_INTERFACE table and current value is null. |
SB-POREC-20107 |
ASN_TYPE field in RCV_HEADERS_INTERFACE must be ASN or ASBN. |
SB-POREC-20108 |
Processing_Status_Code field in RCV_HEADERS_INTERFACE must be PENDING. |
SB-POREC-20109 |
Receipt_Source_Code field in RCV_HEADERS_INTERFACE must be VENDOR. |
SB-POREC-20110 |
Transaction_Type field in RCV_HEADERS_INTERFACE must be NEW or CANCEL. |
SB-POREC-20111 |
Validation_Flag field in RCV_HEADERS_INTERFACE must be Y or N. |
SB-POREC-20112 |
Auto_Transact_Code field in RCV_HEADERS_INTERFACE must be SHIP or RECEIVE or DELIVER. |
SB-POREC-20113 |
Receipt_Num cannot be NULL when Auto_Transact_Code is SHIP. |
SB-POREC-20114 |
Shipped_Date cannot be NULL when Asn_Type is ASN or ASBN. |
SB-POREC-20115 |
Invoice_Num cannot be NULL when Asn_Type is ASBN. |
SB-POREC-20116 |
Invoice_Date cannot be NULL when Asn_Type is ASBN. |
SB-POREC-20117 |
Total_Invoice_Amount cannot be NULL or negative when Asn_Type is ASBN. |
SB-POREC-20118 |
Both Employee_ID and Employee_Name cannot be null when Auto_Transact_Code is RECEIVE. |
SB-POREC-20119 |
Invalid Vendor_Name. |
SB-POREC20189 |
Shipped_Date cannot be earlier than SYSDATE or EXPECTED_RECEIPT_DATE. |
SB-POREC20190 |
Invalid Employee_name. |
Transactions
The Receiving Transaction Errors are listed in the table.
Table 1–18 Receiving Transaction Errors
Error Code |
Error Message |
---|---|
SB-POREC-20120 |
Interface_Transaction_ID field is mandatory in rcv_transactions_interface table and current value is null. |
SB-POREC-20121 |
Group_ID field is mandatory in rcv_transactions_interface table and current value is null. |
SB-POREC-20122 |
Transaction_Type field is mandatory in rcv_transactions_interface table and current value is null. |
SB-POREC-20123 |
Transaction_Date field is mandatory in rcv_transactions_interface table and current value is null. |
SB-POREC-20124 |
Processing_Status_Code field is mandatory in rcv_transactions_interface table and current value is null. |
SB-POREC-20125 |
Processing_Mode_Code field is mandatory in rcv_transactions_interface table and current value is null. |
SB-POREC-20126 |
Transaction_Status_Code field is mandatory in rcv_transactions_interface table and current value is null. |
SB-POREC-20127 |
Quantity field is mandatory in rcv_transactions_interface table and current value is null. |
SB-POREC-20128 |
Unit_Of_Measure field is mandatory in rcv_transactions_interface table and current value is null. |
SB-POREC-20129 |
Item_Description field is mandatory in rcv_transactions_interface table and current value is null. |
SB-POREC-20130 |
Value required in Document_Line_Num or Item_Num or Vendor_Item_Num or Item_ID or Po_Line_ID in rcv_transactions_interface table and currently all are null. |
SB-POREC-20131 |
Auto_Transact_Code field is mandatory in rcv_transactions_interface table and current value is null. |
SB-POREC-20132 |
Receipt_Source_Code field is mandatory in rcv_transactions_interface table and current value is null. |
SB-POREC-20133 |
Vendor_Site_ID field is mandatory in rcv_transactions_interface table and current value is null. |
SB-POREC-20134 |
Value required in either Vendor_Name or Vendor_Num fields in rcv_transactions_interface table and currently both are null. |
SB-POREC-20135 |
Source_Document_Code field is mandatory in rcv_transactions_interface table and current value is null. |
SB-POREC-20136 |
Value required in Document_Num or Po_Header_ID and currently both are null. |
SB-POREC-20137 |
Header_Interface_ID field is mandatory in rcv_transactions_interface table and current value is null. |
SB-POREC-20138 |
Validation_Flag field is mandatory in rcv_transactions_interface table and current value is null. |
SB-POREC-20139 |
FK Validation. Invalid Routing_Header_ID. |
SB-POREC-20140 |
FK Validation. Invalid Routing_Step_ID. |
SB-POREC-20141 |
FK Validation. Invalid Parent_Transaction_ID. |
SB-POREC-20142 |
FK Validation. Invalid Po_Header_ID. |
SB-POREC-20143 |
FK Validation. Invalid Po_Line_ID. |
SB-POREC-20144 |
FK Validation. Invalid Po_Line_Location_ID. |
SB-POREC-20145 |
FK Validation. Invalid Inv_Transaction_ID. |
SB-POREC-20146 |
FK Validation. Invalid Po_Distribution_ID. |
SB-POREC-20147 |
FK Validation. Invalid Po_Release_ID. |
SB-POREC-20148 |
Foreign Key Validation. Invalid Requisition_Line_ID. |
SB-POREC-20149 |
FK Validation. Invalid Requisition_Distribution_ID. |
SB-POREC-20150 |
FK Validation. Invalid Inspection_Quality_Code. |
SB-POREC-20151 |
FK Validation. Invalid Charge_Account_ID. |
SB-POREC-20152 |
FK Validation. Invalid Employee_ID. |
SB-POREC-20153 |
FK Validation. Invalid Wip_Entity_ID. |
SB-POREC-20154 |
FK Validation. Invalid Item_ID. |
SB-POREC-20155 |
FK Validation. Invalid Transportation_Account_ID. |
SB-POREC-20156 |
FK Validation. Invalid Wip_Line_ID. |
SB-POREC-20157 |
FK Validation. Invalid Repetitive_Schedule_ID. |
SB-POREC-20158 |
Foreign Key Validation. Invalid Wip_Entity_ID for wip_operations. |
SB-POREC-20159 |
FK Validation. Invalid Wip_Entity_ID for wip_operations_resources. |
SB-POREC-20160 |
FK Validation. Invalid Bom_Resource_ID. |
SB-POREC-20161 |
FK Validation. Invalid Department_Code. |
SB-POREC-20162 |
FK Validation. Invalid Freight_Carrier_Code. |
SB-POREC-20163 |
FK Validation. Invalid SubInventory. |
SB-POREC-20164 |
FK Validation. Invalid Locator_ID. |
SB-POREC-20165 |
FK Validation. Invalid Uom_Code. |
SB-POREC-20166 |
FK Validation. Invalid Currency_Conversion_Type. |
SB-POREC-20167 |
FK Validation. Invalid Reason_ID. |
SB-POREC-20168 |
FK Validation. Invalid Source_Doc_Unit_Of_Measure. |
SB-POREC-20170 |
FK Validation. Invalid Shipment_Header_ID. |
SB-POREC-20171 |
FK Validation. Invalid Shipment_Line_ID. |
SB-POREC-20172 |
FK Validation. Invalid Primary_Unit_Of_Measure. |
SB-POREC-20173 |
Value required in any one of Item_Category or Category_ID or Document_Line_Num or Po_Line_ID field in rcv_transactions_interface. |
SB-POREC-20174 |
Transaction_Type must be SHIP or RECEIVE. |
SB-POREC-20175 |
Processing_Status_Code must be PENDING. |
SB-POREC-20176 |
Processing_Mode_Code must be BATCH. |
SB-POREC-20177 |
Auto_Transact_Code must be RECEIVE or DELIVER or SHIP. |
SB-POREC-20178 |
Receipt_Source_Code must be VENDOR. |
SB-POREC-20179 |
Source_Document_Code must be PO. |
SB-POREC-20180 |
Header_Interface_ID value not found in rcv_headers_interface. |
SB-POREC-20181 |
Validation_Flag must be Y or N. |
SB-POREC-20182 |
Employee_ID cannot be null when Transaction_Type is DELIVER. |
SB-POREC-20183 |
Valid Group_ID not found in rcv_headers_interface. |
SB-POREC-20184 |
Invalid Ship_To_Location_Code or Ship_To_Location_ID when ASN_TYPE is ASN. |
SB-POREC-20185 |
To_Organization_Code and To_Organization_ID, both cannot be null. |
SB-POREC-20186 |
There must be a valid Destination_Type_Code when Auto_Transact_Code is DELIVER. |
SB-POREC-20187 |
Invalid Expected_Receipt_Date. |
SB-POREC-20188 |
Transaction_Status_Code must be ERROR or COMPLETED. |
SB-POREC-20191 |
Invalid Item_Category. |
SB-POREC-20192 |
Invalid Location_Code. |
SB-POREC-20193 |
Invalid Vendor_Name. |
SB-POREC-20194 |
Invalid Vendor_Num. |
The Requisition Errors are listed in the table.
Table 1–19 Requisition Errors
Error Code |
Error Message |
---|---|
SB-POREQ-20100 |
Interface_Source_Code is mandatory and the current value is NULL. |
SB-POREQ-20101 |
Destination_Type_Code is mandatory and the current value is NULL. |
SB-POREQ-20102 |
Authorization_Status is mandatory and the current value is NULL. |
SB-POREQ-20103 |
Quantity is mandatory and the current value is NULL. |
SB-POREQ-20104 |
Preparer_ID and Preparer_Name values are NULL. Either one must have a value. |
SB-POREQ-20105 |
Charge_Account_ID and Charge_Account_Segment1 values are NULL. Either one must have a value. |
SB-POREQ-20106 |
Destination_Organization_ID and Destination_Organization_Code values are NULL. Either one must have a value. |
SB-POREQ-20107 |
Deliver_To_Location_ID and Deliver_To_Location_Code values are NULL. Either one must have a value. |
SB-POREQ-20108 |
Deliver_To_Requestor_ID and Deliver_To_Requestor_Name values are NULL. Either one must have a value. |
SB-POREQ-20109 |
If Currency_Code value present Rate_Date and Rate_Type are mandatory. |
SB-POREQ-20110 |
If Project_Accounting_Context is Y then you must enter relevent project accounting info like project_id,task_id,expenditure_type and expenditure_org_id. |
SB-POREQ-20111 |
If Destination_Type_code is INVENTORY then you must enter Destination_Subinventory and Item_ID. |
SB-POREQ-20112 |
If Source_Type_Code is INVENTORY then you must enter Item_ID. |
SB-POREQ-20113 |
If Destination_Type_Code is EXPENSE or SHOP FLOOR then you must Source_Type_Code. |
SB-POREQ-20114 |
Requisition_Type value either INTERNAL or PURCHASE. |
SB-POREQ-20115 |
Requisition Header ID is invalid,FK validation failed against po_requisition_headers_all table. |
SB-POREQ-20116 |
Category ID is invalid,FK validation failed against mtl_categories_b table. |
SB-POREQ-20117 |
Unit_Of_Measure is invalid,FK validation failed against mtl_units_of_measure_tl table. |
SB-POREQ-20118 |
Line_Type_ID is invalid,FK validation failed against po_line_types_b table. |
SB-POREQ-20119 |
UN_Number_ID is invalid,FK validation failed against po_un_numbers_b table. |
SB-POREQ-20120 |
Hazard_Class_ID is invalid,FK validation failed against po_hazard_classes_b table. |
SB-POREQ-20121 |
WIP_Entity_ID is invalid,FK validation failed against wip_entities table. |
SB-POREQ-20122 |
WIP_Line_ID is invalid,FK validation failed against wip_lines table. |
SB-POREQ-20123 |
WIP_Entity_ID or Dest_Org_ID or Wip_Operation_Seq_Num or Wip_Rept_Sch_ID either one is invalid,FK validation failed against wip_operations table. |
SB-POREQ-20124 |
WIP_Entity_ID or Dest_Org_ID or Wip_Operation_Seq_Num or Wip_Rept_Sch_ID or Resource_Seq_Num either one is invalid,FK validation failed against wip_operation_resources table. |
SB-POREQ-20125 |
WIP_Repetitive_Schedule_ID or Dest_Org_ID either one is invalid,FK validation failed against wip_repetitive_schedules table. |
SB-POREQ-20126 |
Requisition_Line_ID is invalid,FK validation failed against po_requisition_lines_all table. |
SB-POREQ-20127 |
Src_Org_ID is invalid,FK validation failed against org_organization_definitions table. |
SB-POREQ-20128 |
Dest_Org_ID is invalid,FK validation failed against org_organization_definitions table. |
SB-POREQ-20129 |
Source_Subinventory is invalid for a given Src_Org_ID,FK validation failed against MTL_Secondary_Inventories table. |
SB-POREQ-20130 |
Destination_Subinventory is invalid for a given Dest_Org_ID,FK validation failed against MTL_Secondary_Inventories table. |
SB-POREQ-20131 |
Deliver_To_Requestor_ID is invalid,FK validation failed against hr_employees table. |
SB-POREQ-20132 |
Suggested_Buyer_ID is invalid,FK validation failed against po_agents table. |
SB-POREQ-20133 |
Suggested_Vendor_ID is invalid,FK validation failed against po_vendors table. |
SB-POREQ-20134 |
Suggested_Vendor_Site_ID is invalid,FK validation failed against po_vendor_sites_all table. |
SB-POREQ-20135 |
Req_Distribution_ID is invalid,FK validation failed against Po_Req_Distributions_All table. |
SB-POREQ-20136 |
Suggested_Vendor_Contact_ID is invalid,FK validation failed against Po_Vendor_Contacts table. |
SB-POREQ-20137 |
Note1_ID is invalid,FK validation failed against Po_Notes table. |
SB-POREQ-20138 |
Accrual_Account_ID is invalid,FK validation failed against Gl_Code_Combinations table. |
SB-POREQ-20139 |
Variance_Account_ID is invalid,FK validation failed against Gl_Code_Combinations table. |
SB-POREQ-20140 |
Budget_Account_ID is invalid,FK validation failed against Gl_Code_Combinations table. |
SB-POREQ-20141 |
Ussgl_Transaction_Code is invalid,FK validation failed against gl_ussgl_transaction_codes table. |
SB-POREQ-20142 |
Currency_Code is invalid,FK validation failed against fnd_currencies table. |
SB-POREQ-20143 |
Rate is invalid,FK validation failed against gl_daily_conversion_rates_r10 table. |
SB-POREQ-20144 |
Rate_Type is invalid,FK validation failed against gl_daily_conversion_types table. |
SB-POREQ-20145 |
Approver_ID is invalid,FK validation failed against hr_employees table. |
SB-POREQ-20146 |
Autosource_Doc_Header_ID is invalid,FK validation failed against po_autosource_documents_all table. |
SB-POREQ-20147 |
Project_ID is invalid,FK validation failed against pa_projects_all table. |
SB-POREQ-20148 |
Task_ID is invalid,FK validation failed against pa_tasks table. |
SB-POREQ-20149 |
Note2_ID is invalid,FK validation failed against po_notes table. |
SB-POREQ-20150 |
Note3_ID is invalid,FK validation failed against po_notes table. |
SB-POREQ-20151 |
Note4_ID is invalid,FK validation failed against po_notes table. |
SB-POREQ-20152 |
Note5_ID is invalid,FK validation failed against po_notes table. |
SB-POREQ-20153 |
Note6_ID is invalid,FK validation failed against po_notes table. |
SB-POREQ-20154 |
Note7_ID is invalid,FK validation failed against po_notes table. |
SB-POREQ-20155 |
Note8_ID is invalid,FK validation failed against po_notes table. |
SB-POREQ-20156 |
Note9_ID is invalid,FK validation failed against po_notes table. |
SB-POREQ-20157 |
Note10_ID is invalid,FK validation failed against po_notes table. |
SB-POREQ-20158 |
Expenditure_Type is invalid,FK validation failed against pa_expenditure_types table. |
SB-POREQ-20159 |
Document_Type_Code is invalid,FK validation failed against po_document_types_all_b table. |
SB-POREQ-20160 |
Kanban_Card_ID is invalid,FK validation failed against mtl_kanban_cards table. |
SB-POREQ-20161 |
Preparer_ID is invalid,FK validation failed against hr_employees table. |
SB-POREQ-20162 |
Item_ID is invalid,FK validation failed against mtl_system_items_b table. |
SB-POREQ-20163 |
Item_Revision is invalid,FK validation failed against mtl_item_revisions table. |
SB-POREQ-20164 |
Charge_Account_ID is invalid,FK validation failed against gl_code_combinations table. |
SB-POREQ-20165 |
If Dest_Type_Code is INVENTORY then item must be stock enabled for dest org. If Dest_Subinventory present then item must be valid either in subinventory or to a subinventory. |
SB-POREQ-20166 |
If Dest_Type_Code is EXPENSE then item must be purchasing enabled for purchasing and dest org. |
SB-POREQ-20167 |
If Dest_Type_Code is SHOP FLOOR then item must be an outise-operation item and purchasing enabled for purchasing and dest org. |
SB-POREQ-20168 |
If Src_Type_Code is INVENTORY then the item must be stock enabled for the src org and internal-order-enabled for the purchasing. |
SB-POREQ-20169 |
If Src_Type_Code is VENDOR then the item must be purchasing enabled for the purchasing and dest org id. |
SB-POREQ-20170 |
Deliver_To_Location_ID is invalid,FK validation failed against Hr_Locations table. |
SB-POREQ-20171 |
category_id is invalid for the given item. |
This section provides a description of each of the following Financial Budget error codes.
This section provides a description of each of the Accounts Payable error codes.
Table 1–20 Accounts Payable Errors
Error Code |
Error Message |
---|---|
SB-AP-INVOICE-20000 |
INVOICE_ID cannot be NULL. |
SB-AP-INVOICE-20001 |
PO_NUMBER does not exist in PO_HEADERS. |
SB-AP-INVOICE-20002 |
VENDOR_ID does not exist in PO_VENDORS. |
SB-AP-INVOICE-20003 |
VENDOR_NUM does not exist in PO_VENDORS. |
SB-AP-INVOICE-20004 |
VENDOR_NAME does not exist in PO_VENDORS. |
SB-AP-INVOICE-20005 |
VENDOR_SITE_ID does not exist in PO_VENDOR_SITES. |
SB-AP-INVOICE-20006 |
VENDOR_SITE_CODE does not exist in PO_VENDOR_SITES. |
SB-AP-INVOICE-20007 |
INVOICE_CURRENCY_CODE does not exist in FND_CURRENCIES. |
SB-AP-INVOICE-20008 |
EXCHANGE_RATE_TYPE does not exist in GL_DAILY_CONVERSION_TYPES. |
SB-AP-INVOICE-20009 |
TERMS_ID does not exist in AP_TERMS. |
SB-AP-INVOICE-20010 |
TERMS_NAME does not exist in AP_TERMS. |
SB-AP-INVOICE-20011 |
AWT_GROUP_ID does not exist in AP_AWT_GROUPS. |
SB-AP-INVOICE-20012 |
AWT_GROUP_NAME does not exist in AP_AWT_GROUPS. |
SB-AP-INVOICE-20013 |
PREPAY_NUM does not exist in AP_INVOICES. |
SB-AP-INVOICE-20020 |
INVOICE_TYPE_LOOKUP_CODE does not exist in AP_LOOKUP_CODES. |
SB-AP-INVOICE-20021 |
PAYMENT_METHOD_LOOKUP_CODE does not exist in AP_LOOKUP_CODES. |
SB-AP-INVOICE-20022 |
SOURCE does not exist in AP_LOOKUP_CODES. |
SB-AP-INVOICE-20023 |
INVOICE_NUM cannot be NULL. |
SB-AP-INVOICE-20024 |
SOURCE cannot be NULL. |
SB-AP-INVOICE-20025 |
INVOICE_NUM and VENDOR_ID should be unique in AP_INVOICES_ALL. |
SB-AP-INVOICE-20026 |
VENDOR_ID or VENDOR_NUM or VENDOR_NAME or PO_NUMBER should be entered. |
SB-AP-INVOICE-20027 |
VENDOR_SITE_ID or VENDOR_SITE_CODE or PO_NUMBER should be entered. |
SB-AP-INVOICE-20028 |
EXCHANGE_RATE required if INVOICE_CURRENCY_CODE is entered and EXCHANGE_RATE_TYPE is User. |
SB-AP-INVOICE-20029 |
EXCHANGE_DATE required if INVOICE_CURRENCY_CODE is entered. |
SB-AP-INVOICE-20030 |
WORKFLOW_FLAG Should be in Y,S,D or NULL. |
SB-AP-INVOICE-20031 |
ACCTS_PAY_CODE_COMBINATION_ID does not exists in GL_CODE_COMBINATIONS. |
SB-AP-INVOICE-20032 |
ORG_ID does not exists in HR_ORGANIZATION_UNITS_V. |
SB-AP-INVLIN-20100 |
INVOICE_ID is a required column. Enter a valid value. |
SB-AP-INVLIN-20101 |
LINE_NUMBER is a required column. Enter a valid value. |
SB-AP-INVLIN-20102 |
LINE_TYPE_LOOKUP_CODE is a required column. Enter a valid value. |
SB-AP-INVLIN-20103 |
AMOUNT is a required column. Enter a valid value. |
SB-AP-INVLIN-20111 |
INVOICE_ID does NOT exist IN TABLE SB_AP_INVOICES_INTERFACE. |
SB-AP-INVLIN-20112 |
Valid values for LINE_TYPE_LOOKUP_CODE column are ITEM,TAX,MISCELLANEOUS,FREIGHT. |
SB-AP-INVLIN-20113 |
LINE_GROUP_NUMBER value must be a positive whole number. |
SB-AP-INVLIN-20114 |
PO_NUMBER does NOT exist IN TABLE PO_HEADERS. |
SB-AP-INVLIN-20115 |
PO_HEADER_ID does NOT exist IN TABLE PO_HEADERS. |
SB-AP-INVLIN-20116 |
PO_LINE_ID does NOT exist IN TABLE PO_LINES. |
SB-AP-INVLIN-20117 |
PO_LINE_NUMBER does NOT exist IN TABLE PO_LINES. |
SB-AP-INVLIN-20118 |
PO_LINE_LOCATION_ID does NOT exist IN TABLE PO_LINE_LOCATIONS. |
SB-AP-INVLIN-20119 |
PO_SHIPMENT_NUM does NOT exist IN TABLE PO_LINE_LOCATIONS. |
SB-AP-INVLIN-20120 |
PO_DISTRIBUTION_NUM does NOT exist IN TABLE PO_DISTRIBUTIONS. |
SB-AP-INVLIN-20121 |
PO_UNIT_OF_MEASURE does NOT exist IN TABLE PO_DISTRIBUTIONS |
SB-AP-INVLIN-20122 |
INVENTORY_ITEM_ID does NOT exist IN TABLE MTL_SYSTEM_ITEMS. |
SB-AP-INVLIN-20123 |
ITEM_DESCRIPTION does NOT exist IN TABLE PO_LINES. |
SB-AP-INVLIN-20124 |
QUANTITY_INVOICED value must be a positive whole number. |
SB-AP-INVLIN-20125 |
SHIP_TO_LOCATION_CODE does NOT exist IN TABLE PO_LINE_LOCATIONS. |
SB-AP-INVLIN-20126 |
DISTRIBUTION_SET_ID does NOT exist IN TABLE AP_DISTRIBUTION_SETS. |
SB-AP-INVLIN-20127 |
DISTRIBUTION_SET_NAME does NOT exist IN TABLE AP_DISTRIBUTION_SETS. |
SB-AP-INVLIN-20128 |
DIST_CODE_CONCATENATED does NOT exist IN TABLE GL_CODE_COMBINATIONS. |
SB-AP-INVLIN-20129 |
AWT_GROUP_ID does NOT exist IN TABLE AP_AWT_GROUPS. |
SB-AP-INVLIN-20130 |
AWT_GROUP_NAME does NOT exist IN TABLE AP_AWT_GROUPS. |
SB-AP-INVLIN-20131 |
PO_RELEASE_ID does NOT exist IN TABLE PO_RELEASES. |
SB-AP-INVLIN-20132 |
RELEASE_NUM does NOT exist IN TABLE PO_RELEASES. |
SB-AP-INVLIN-20133 |
RCV_TRANSACTION_ID does NOT exist IN TABLE RCV_TRANSACTIONS. |
SB-AP-INVLIN-20134 |
ORG_ID does NOT exist IN VIEW HR_ORGANIZATION_UNITS_V. |
SB-AP-INVLIN-20135 |
DIST_CODE_COMBINATION_ID does NOT exist IN TABLE GL_CODE_COMBINATIONS. |
SB-AP-INVLIN-20136 |
ACCOUNTING_DATE,the date must be an open accounting period. |
SB-AP-INVLIN-20138 |
Valid VALUES FOR PRORATE_ACROSS_FLAG are Y,N. |
SB-AP-INVLIN-20139 |
INCOME_TAX_REGION does NOT exist IN AP_INCOME_TAX_TYPES TABLE AND should be active. |
SB-AP-INVLIN-20140 |
PO_DISTRIBUTION_ID does NOT exist IN TABLE PO_DISTRIBUTIONS. |
SB-AP-INVLIN-20141 |
’TYPE_1099 does NOT exist IN AP_INCOME_TAX_TYPES TABLE AND should be active. |
SB-AP-INVLIN-20142 |
TAX_CODE does NOT exist IN AP_INCOME_TAX_TYPES TABLE AND should be active. |
This section provides a description of each of the Accounts Receivable error codes.
The Auto Invoice Errors are listed in the table.
Table 1–21 Auto Invoice Errors
Error Code |
Error Message |
---|---|
SB-AR-DIST-10400 |
ACCOUNT_CLASS cannot be NULL. |
SB-AR-DIST-10401 |
CODE_COMBINATION_ID does not exists in GL_CODE_COMBINATIONS table. |
SB-AR-DIST-10402 |
ACCOUNT_CLASS should be either REV, FREIGHT, TAX, REC, CHARGES, UNBILL, UNEARN. |
SB-AR-LINES-10600 |
CONVERSION_TYPE is a required column. Enter a valid value. |
SB-AR-LINES-10601 |
BATCH_SOURCE_NAME is a required column. Enter a valid value. |
SB-AR-LINES-10602 |
SET_OF_BOOKS_ID is a required column. Enter a valid value. |
SB-AR-LINES-10603 |
LINE_TYPE is a required column. Enter a valid value. |
SB-AR-LINES-10604 |
DESCRIPTION is a required column. Enter a valid value. |
SB-AR-LINES-10605 |
CURRENCY_CODE is a required column. Enter a valid value. |
SB-AR-LINES-10606 |
LAST_UPDATED_BY is a required column. Enter a valid value. |
SB-AR-LINES-10607 |
LAST_UPDATE_DATE is a required column. Enter a valid value. |
SB-AR-LINES-10608 |
CREATED_BY is a required column. Enter a valid value. |
SB-AR-LINES-10609 |
CREATION_DATE is a required column. Enter a valid value. |
SB-AR-LINES-10625 |
CONVERSION_TYPE does not exists in GL_DAILY_CONVERSION_TYPES table. |
SB-AR-LINES-10626 |
SET_OF_BOOKS_ID does not exists in AR_SYSTEM_PARAMETERS table. |
SB-AR-LINES-10627 |
CURRENCY_CODE does not exists in FND_CURRENCIES table. |
SB-AR-LINES-10650 |
Valid values for LINE_TYPE column are LINE,TAX,FREIGHT and CHARGES. |
SB-AR-LINES-10651 |
ACCOUNTING_RULE_ID value should match with RULE_ID value of RA_RULES Table. |
SB-AR-LINES-10652 |
ACCOUNTING_RULE_NAME value should match with NAME value of RA_RULES Table. |
SB-AR-LINES-10653 |
AGREEMENT_NAME value should match with NAME value of SO_AGREEMENTS Table. |
SB-AR-LINES-10654 |
AGREEMENT_ID value should match with ID value of SO_AGREEMENTS Table. |
SB-AR-LINES-10655 |
BATCH_SOURCE_NAME value should match with NAME value of RA_BATCH_SOURCES_ALL Table. |
SB-AR-LINES-10656 |
CONS_BILLING_NUMBER must not already exist in AR_CONS_INV_ALL table. |
SB-AR-LINES-10657 |
CONVERSION_RATE should be not null if CONVERSION_TYPE is USER and CONVERSION_RATE should be null if CONVERSION_TYPE is not USER. |
SB-AR-LINES-10658 |
Valid values for CREDIT_METHOD_FOR_ACCT_RULE column are PRORATE,LIFO,UNIT. |
SB-AR-LINES-10659 |
Valid values for CREDIT_METHOD_FOR_INSTALLMENTS column are PRORATE,LIFO,UNIT. |
SB-AR-LINES-10660 |
CUST_TRX_TYPE_ID value should match with CUST_TRX_TYPE_ID value of RA_BATCH_SOURCES_ALL Table. |
SB-AR-LINES-10661 |
CUST_TRX_TYPE_NAME value should match with NAME value of RA_BATCH_SOURCES_ALL Table. |
SB-AR-LINES-10662 |
FOB_POINT value should match with LOOKUP_CODE value of AR_LOOKUPS Table where LOOKUP_TYPE is FOB. |
SB-AR-LINES-10663 |
INVENTORY_ITEM_ID value should match with INVENTORY_ITEM_ID value of MTL_SYSTEM_ITEMS Table. |
SB-AR-LINES-10664 |
MEMO_LINE_ID value should match with MEMO_LINE_ID value of AR_MEMO_LINES_ALL_B Table. |
SB-AR-LINES-10665 |
MEMO_LINE_NAME value should match with NAME value of AR_MEMO_LINES_ALL_B Table. |
SB-AR-LINES-10666 |
Enter the appropriate value in ORIG_SYSTEM_BILL_ADDRESS_ID. |
SB-AR-LINES-10667 |
Enter the appropriate value in ORIG_SYSTEM_BILL_ADDRESS_REF. |
SB-AR-LINES-10668 |
Enter the appropriate value in ORIG_SYSTEM_BILL_CONTACT_ID. |
SB-AR-LINES-10669 |
Enter the appropriate value in ORIG_SYSTEM_BILL_CONTACT_REF. |
SB-AR-LINES-10670 |
ORIG_SYSTEM_BILL_CUSTOMER_ID value should match with CUST_ACCOUNT_ID value of HZ_CUST_ACCOUNTS Table. |
SB-AR-LINES-10671 |
ORIG_SYSTEM_BILL_CUSTOMER_REF value should match with ORIG_SYSTEM_REFERENCE value of HZ_CUST_ACCOUNTS Table. |
SB-AR-LINES-10672 |
Enter the appropriate value in ORIG_SYSTEM_SHIP_ADDRESS_ID. |
SB-AR-LINES-10673 |
Enter the appropriate value in ORIG_SYSTEM_SHIP_ADDRESS_REF. |
SB-AR-LINES-10674 |
Enter the appropriate value in ORIG_SYSTEM_SHIP_CONTACT_ID. |
SB-AR-LINES-10675 |
Enter the appropriate value in ORIG_SYSTEM_SHIP_CONTACT_REF. |
SB-AR-LINES-10676 |
ORIG_SYSTEM_SHIP_CUSTOMER_ID value should match with CUST_ACCOUNT_ID value of HZ_CUST_ACCOUNTS Table. |
SB-AR-LINES-10677 |
ORIG_SYSTEM_SHIP_CUSTOMER_REF value should match with ORIG_SYSTEM_REFERENCE value of HZ_CUST_ACCOUNTS Table. |
SB-AR-LINES-10678 |
ORIG_SYSTEM_SOLD_CUSTOMER_ID value should match with CUST_ACCOUNT_ID value of HZ_CUST_ACCOUNTS Table. |
SB-AR-LINES-10679 |
ORIG_SYSTEM_SOLD_CUSTOMER_REF value should match with ORIG_SYSTEM_REFERENCE value of HZ_CUST_ACCOUNTS Table. |
SB-AR-LINES-10680 |
PRIMARY_SALESREP_ID value should match with SALESREP_ID value of RA_SALESREPS Table. |
SB-AR-LINES-10681 |
PRIMARY_SALESREP_NUMBER value should match with SALESREP_NUMBER value of RA_SALESREPS Table. |
SB-AR-LINES-10682 |
PRINTING_OPTION value should match with LOOKUP_CODE value of AR_LOOKUPS Table. |
SB-AR-LINES-10683 |
REASON_CODE value should match with LOOKUP_CODE value of AR_LOOKUPS Table. |
SB-AR-LINES-10684 |
REASON_CODE_MEANING value should match with MEANING value of AR_LOOKUPS Table. |
SB-AR-LINES-10685 |
RECEIPT_METHOD_ID value should match with RECEIPT_METHOD_ID value of AR_RECEIPT_METHODS Table. |
SB-AR-LINES-10686 |
RECEIPT_METHOD_NAME value should match with NAME value of AR_RECEIPT_METHODS Table. |
SB-AR-LINES-10687 |
Enter the appropriate value in REFERENCE_LINE_CONTEXT. |
SB-AR-LINES-10688 |
REFERENCE_LINE_ID value should match with CUSTOMER_TRX_LINE_ID value of RA_CUSTOMER_TRX_LINES Table. |
SB-AR-LINES-10689 |
Enter the appropriate value in RELATED_BATCH_SOURCE_NAME. |
SB-AR-LINES-10690 |
RELATED_CUSTOMER_TRX_ID value should match with CUSTOMER_TRX_ID value of RA_CUSTOMER_TRX_ALL Table. |
SB-AR-LINES-10692 |
Enter the appropriate value in RELATED_TRX_NUMBER. |
SB-AR-LINES-10694 |
TAX_CODE value should match with TAX_CODE value of AR_VAT_TAX Table.” |
SB-AR-LINES-10695 |
Enter the appropriate value in TAX_EXEMPT_FLAG. |
SB-AR-LINES-10696 |
TAX_EXEMPT_REASON_CODE value should match with LOOKUP_CODE value of AR_LOOKUPS Table. |
SB-AR-LINES-10697 |
TAX_EXEMPT_REASON_CODE_MEANING value should match with MEANING value of AR_LOOKUPS Table. |
SB-AR-LINES-10698 |
TERM_ID value should match with TERM_ID value of RA_TERMS Table. |
SB-AR-LINES-10699 |
TERM_NAME value should match with NAME value of RA_TERMS Table. |
SB-AR-LINES-10700 |
TERRITORY_ID value should match with TERRITORY_ID value of RA_TERRITORIES Table. |
SB-AR-LINES-10701 |
TRX_NUMBER value should not match with TRX_NUMBER value of RA_CUSTOMER_TRX_ALL Table. |
SB-AR-LINES-10702 |
UOM_CODE value should match with UOM_CODE value of MTL_UNITS_OF_MEASURE Table. |
SB-AR-LINES-10703 |
UOM_NAME value should match with UNIT_OF_MEASURE value of MTL_UNITS_OF_MEASURE Table. |
SB-AR-LINES-10705 |
AMOUNT value should be NULL when LINE_TYPE = CHARGES. |
SB-AR-LINES-10706 |
AMOUNT_INCLUDES_TAX_FLAG should be either Y or N. |
SB-AR-LINES-10707 |
GL_DATE must be OPEN or FUTURE ENTRY accounting period in GL_PERIOD_STATUSES. |
SB-AR-LINES-10708 |
INVOICING_RULE_ID value should exist in RULE_ID column of RA_RULES Table. |
SB-AR-LINES-10709 |
CUSTOMER_BANK_ACCOUNT_ID value should exist in BANK_ACCOUNT_ID column of AP_BANK_ACCOUNTS_ALL Table. |
SB-AR-LINES-10710 |
CUSTOMER_BANK_ACCOUNT_NAME value should exist in BANK_ACCOUNT_NAME column of AP_BANK_ACCOUNTS_ALL Table. |
SB-AR-SALES-10500 |
INTERFACE_SALESCREDIT_ID cannot be NULL. |
SB-AR-SALES-10530 |
SALES_CREDIT_AMOUNT_SPLIT AND SALES_CREDIT_PERCENT_SPLIT cannot be Null/Not Null. |
SB-AR-SALES-10531 |
SALES_CREDIT_AMOUNT_SPLIT cannot be Null and Should be between 0 and 100. |
SB-AR-SALES-10532 |
SALES_CREDIT_TYPE_ID cannot be Null and does not exist in SO_SALES_CREDIT_TYPES Table. |
SB-AR-SALES-10533 |
SALES_CREDIT_TYPE_NAME cannot be Null and SALES_CREDIT_TYPE_NAME does not exist in SO_SALES_CREDIT_TYPES Table. |
SB-AR-SALES-10534 |
SALESREP_ID cannot be Null and SALESREP_ID does not exist in RA_SALESREPS. |
SB-AR-SALES-10535 |
SALESREP_NUMBER does not exist in RA_SALESREPS. |
The Auto Lock Box Errors are as listed in the table.
Table 1–22 Auto Lock Box Errors
Error Code |
Error Message |
---|---|
SB-AR-PAYMENT-10800 |
RECORD_TYPE is a required column. Enter a valid value. |
SB-AR-PAYMENT-10801 |
ORIGINATION is a required column for record_type as RECEIPT. Enter a valid value. |
SB-AR-PAYMENT-10802 |
BATCH_NAME is a required column for record_type as RECEIPT. Enter a valid value. |
SB-AR-PAYMENT-10803 |
GL_DATE is a required column for record_type as RECEIPT. Enter a valid value. |
SB-AR-PAYMENT-10804 |
REMITTANCE_AMOUNT is a required column for record_type as RECEIPT. Enter a valid value. |
SB-AR-PAYMENT-10805 |
RECEIPT_METHOD_ID is a required column for record_type as RECEIPT. Enter a valid value. |
SB-AR-PAYMENT-10815 |
TRANSMISSION_ID does not exists in AR_TRANSMISSIONS_ALL table. |
SB-AR-PAYMENT-10816 |
RECEIPT_METHOD_ID does not exists in AR_RECEIPT_METHODS table. |
SB-AR-PAYMENT-10817 |
CUSTOMER_SITE_USE_ID does not exists in HZ_CUST_SITE_USES_ALL table. |
SB-AR-PAYMENT-10818 |
CUSTOMER_BANK_ACCOUNT_ID does not exists in AP_BANK_ACCOUNTS_ALL table. |
SB-AR-PAYMENT-10819 |
CUSTOMER_ID does not exists in HZ_CUST_ACCOUNTS table. |
SB-AR-PAYMENT-10850 |
RECORD_TYPE value should match with RECORD_IDENTIFIER value of AR_TRANS_RECORD_FORMATS Table. |
SB-AR-PAYMENT-10851 |
TRANSMISSION_ID value should match with TRANSMISSION_ID value of AR_TRANSMISSIONS_ALL Table. |
SB-AR-PAYMENT-10852 |
CUSTOMER_BANK_ACCOUNT_ID value should match with EXTERNAL_BANK_ACCOUNT_ID value of AP_BANK_ACCOUNT_USES_ALL Table. |
SB-AR-PAYMENT-10853 |
Valid value for the STATUS field is either NULL or AR_PLB_NEW_RECORD. |
SB-AR-PAYMENT-10854 |
ORIGINATION value should match with BANK_ORIGINATION_NUMBER value of AR_LOCKBOXES_ALL Table. |
SB-AR-PAYMENT-10855 |
EXCHANGE_RATE_TYPE value should match with LOOKUP_CODE value of AR_LOOKUPS Table. |
SB-AR-PAYMENT-10856 |
CUSTOMER_BANK_NAME value should match with the BANK_NAME value of AP_BANK_BRANCHES table. |
SB-AR-PAYMENT-10857 |
REMITTANCE_BANK_NAME value should match with the BANK_NAME value of AP_BANK_BRANCHES table. |
SB-AR-PAYMENT-10858 |
CUSTOMER_BANK_BRANCH_NAME value should match with the BANK_BRANCH_NAME value of AP_BANK_BRANCHES table. |
SB-AR-PAYMENT-10859 |
CURRENCY_CODE value should match with the CURRENCY_CODE value of FND_CURRENCIES table. |
SB-AR-PAYMENT-10860 |
TRANSIT_ROUTING_NUMBER value should match with BANK_NUM value of AP_BANK_BRANCHES Table. |
SB-AR-PAYMENT-10861 |
ACCOUNT value should match with BANK_ACCOUNT_NUM value of AP_BANK_ACCOUNTS_ALL Table. |
SB-AR-PAYMENT-10862 |
CUSTOMER_BANK_ACCOUNT_ID value should match with BANK_ACCOUNT_ID value of AP_BANK_ACCOUNTS_ALL. |
SB-AR-PAYMENT-10863 |
LOCKBOX_NUMBER value should match with LOCKBOX_NUMBER value of AR_LOCKBOXES_ALL table. |
SB-AR-PAYMENT-10864 |
BATCH_NAME value should match with NAME value of AR_BATCHES_ALL table. |
The Customer Interface Errors are as listed in the table.
Table 1–23 Customer Interface Errors
Error Code |
Error Message |
---|---|
SB-AR-PHONES-10700 |
CREATED_BY cannot be NULL. |
SB-AR-PHONES-10701 |
CREATION_DATE cannot be NULL. |
SB-AR-PHONES-10702 |
INSERT_UPDATE_FLAG cannot be NULL. |
SB-AR-PHONES-10703 |
LAST_UPDATED_BY cannot be NULL. |
SB-AR-PHONES-10704 |
LAST_UPDATE_DATE cannot be NULL. |
SB-AR-PHONES-10705 |
ORIG_SYSTEM_CONTACT_REF cannot be NULL. |
SB-AR-PHONES-10706 |
ORIG_SYSTEM_TELEPHONE_REF cannot be NULL. |
SB-AR-PHONES-10707 |
ORIG_SYSTEM_CUSTOMER_REF cannot be NULL. |
SB-AR-PHONES-10708 |
CONTACT_JOB_TITLE does not exist in AR_LOOKUPS table. |
SB-AR-PHONES-10709 |
CONTACT_TITLE does not exist in AR_LOOKUPS table. |
SB-AR-PHONES-10710 |
ORIG_SYSTEM_CUSTOMER_REF does not exist in HZ_CUST_ACCOUNTS table. |
SB-AR-PHONES-10711 |
ORIG_SYSTEM_ADDRESS_REF does not exist in HZ_CUST_ACCT_SITES_ALL table. |
SB-AR-PHONES-10712 |
ORIG_SYSTEM_CONTACT_REF does not exist in HZ_ORG_CONTACTS table. |
SB-AR-PHONES-10713 |
ORIG_SYSTEM_TELEPHONE_REF does not exist in HZ_CONTACT_POINTS table. |
SB-AR-PHONES-10714 |
TELEPHONE_TYPE does not exist in AR_LOOKUPS table. |
SB-AR-PHONES-10715 |
INSERT_UPDATE_FLAG should be either I or U. |
SB-AR-PHONES-10716 |
TELEPHONE cannot be null if ORIG_SYSTEM_TELEPHONE_REF entered. |
SB-AR-PHONES-10717 |
CONTACT_LAST_NAME cannot be null if ORIG_SYSTEM_CONTACT_REF entered. |
SB-AR-PHONES-10718 |
ORIG_SYSTEM_TELEPHONE_REF cannot be null if TELEPHONE entered. |
SB-AR-PHONES-10719 |
TELEPHONE_TYPE cannot be null if ORIG_SYSTEM_TELEPHONE_REF entered. |
SB-AR-PAY-10300 |
ORIG_SYSTEM_CUSTOMER_REF is a required column. Enter a valid value. |
SB-AR-PAY-10301 |
PAYMENT_METHOD_NAME is a required column. Enter a valid value. |
SB-AR-PAY-10302 |
PRIMARY_FLAG is a required column. Enter a valid value. |
SB-AR-PAY-10303 |
START_DATE is a required column. Enter a valid value. |
SB-AR-PAY-10304 |
LAST_UPDATED_BY is a required column. Enter a valid value. |
SB-AR-PAY-10305 |
LAST_UPDATE_DATE is a required column. Enter a valid value. |
SB-AR-PAY-10306 |
CREATION_DATE is a required column. Enter a valid value. |
SB-AR-PAY-10307 |
CREATED_BY is a required column. Enter a valid value. |
SB-AR-PAY-10315 |
Valid values for PRIMARY_FLAG column are Y,N. |
SB-AR-PAY-10316 |
Valid values for VALIDATED_FLAG column are Y,N. |
SB-AR-PAY-10317 |
PAYMENT_METHOD_NAME does not exist in table AR_RECEIPT_METHODS. |
SB-AR-PAY-10318 |
ORIG_SYSTEM_CUSTOMER_REF does not exist in table RA_CUSTOMERS and SB_RA_CUSTOMERS_INTERFACE. |
SB-AR-PAY-10319 |
ORIG_SYSTEM_ADDRESS_REF does not exist in table RA_ADDRESSES and SB_RA_CUSTOMERS_INTERFACE. |
SB-AR-PAY-10320 |
ORG_ID does not exist IN VIEW HR_ORGANIZATION_UNITS_V. |
SB-AR-BANKS-10200 |
ORIG_SYSTEM_CUSTOMER_REF cannot be NULL. |
SB-AR-BANKS-10201 |
BANK_ACCOUNT_NAME cannot be NULL. |
SB-AR-BANKS-10202 |
PRIMARY_FLAG cannot be NULL. |
SB-AR-BANKS-10203 |
START_DATE cannot be NULL. |
SB-AR-BANKS-10204 |
LAST_UPDATE_DATE cannot be NULL. |
SB-AR-BANKS-10205 |
LAST_UPDATED_BY cannot be NULL. |
SB-AR-BANKS-10206 |
CREATION_DATE cannot be NULL. |
SB-AR-BANKS-10207 |
CREATED_BY cannot be NULL. |
SB-AR-BANKS-10208 |
BANK_ACCOUNT_CURRENCY_CODE cannot be NULL. |
SB-AR-BANKS-10209 |
BANK_ACCOUNT_NUM cannot be NULL. |
SB-AR-BANKS-10210 |
BANK_BRANCH_NAME cannot be NULL. |
SB-AR-BANKS-10211 |
ORIG_SYSTEM_ADDRESS_REF cannot be NULL if the bank details are entered.Also it should be equal to BILL_TO address. |
SB-AR-BANKS-10212 |
BANK_ACCOUNT_CURRENCY_CODE does not exist in FND_CURRENCIES table. |
SB-AR-BANKS-10213 |
BANK_ACCOUNT_NAME does not exist in AP_BANK_ACCOUNTS table. |
SB-AR-BANKS-10214 |
BANK_NUMBER does not exist in AP_BANK_BRANCHES table. |
SB-AR-BANKS-10215 |
BANK_NUM should be unique in AP_BANK_BRANCHES table. |
SB-AR-BANKS-10216 |
BANK_BRANCH_COUNTRY does not exist in FND_TERRITORIES table. |
SB-AR-BANKS-10217 |
END_DATE should be greater than START_DATE. |
SB-AR-BANKS-10218 |
ORIG_SYSTEM_CUSTOMER_REF does not exist in HZ_CUST_ACCOUNTS table. |
SB-AR-BANKS-10219 |
PRIMARY_FLAG should be either Y or N. |
SB-AR-BANKS-10220 |
BANK_NAME,BANK_BRANCH_NAME should be unique in AP_BANK_BRANCHES table. |
SB-AR-BANKS-10221 |
BANK_NAME cannot be NULL. |
SB-AR-BANKS-10222 |
ORIG_SYSTEM_ADDRESS_REF does not exist in HZ_CUST_ACCT_SITES_ALL or SB_RA_CUSTOMERS_INTERFACE table.The address specified must have an active BILL_TO site defined. |
SB-AR-CUST-10000 |
ORIG_SYSTEM_CUSTOMER_REF cannot be NULL. |
SB-AR-CUST-10001 |
SITE_USE_CODE cannot be NULL. |
SB-AR-CUST-10002 |
ORIG_SYSTEM_ADDRESS_REF cannot be NULL. |
SB-AR-CUST-10003 |
INSERT_UPDATE_FLAG cannot be NULL. |
SB-AR-CUST-10004 |
CUSTOMER_NAME cannot be NULL. |
SB-AR-CUST-10005 |
CUSTOMER_NUMBER cannot be NULL. |
SB-AR-CUST-10006 |
CUSTOMER_STATUS cannot be NULL. |
SB-AR-CUST-10007 |
LAST_UPDATED_BY cannot be NULL. |
SB-AR-CUST-10008 |
LAST_UPDATE_DATE cannot be NULL. |
SB-AR-CUST-10009 |
CREATED_BY cannot be NULL. |
SB-AR-CUST-10010 |
CREATION_DATE cannot be NULL. |
SB-AR-CUST-10011 |
LOCATION cannot be NULL. |
SB-AR-CUST-10025 |
SITE_USE_CODE does not exists in AR_LOOKUPS table. |
SB-AR-CUST-10026 |
CUSTOMER_TYPE does not exists in AR_LOOKUPS table. |
SB-AR-CUST-10027 |
ORIG_SYSTEM_PARENT_REF does not exists in RA_CUSTOMERS table. |
SB-AR-CUST-10028 |
CUSTOMER_CATEGORY_CODE does not exists in AR_LOOKUPS table. |
SB-AR-CUST-10029 |
CUSTOMER_CLASS does not exists in AR_LOOKUPS table. |
SB-AR-CUST-10030 |
DEMAND_CLASS_CODE does not exists in FND_COMMON_LOOKUPS table. |
SB-AR-CUST-10031 |
CUST_SHIP_VIA_CODE does not exists in ORG_FREIGHT table. |
SB-AR-CUST-10032 |
LANGUAGE does not exists in FND_LANGUAGES table. |
SB-AR-CUST-10033 |
CUST_TAX_CODE value should match with TAX_CODE value of AR_VAT_TAX Table. |
SB-AR-CUST-10034 |
SITE_USE_TAX_CODE value should match with TAX_CODE value of AR_VAT_TAX Table. |
SB-AR-CUST-10050 |
ADDRESS cannot be NULL. |
SB-AR-CUST-10051 |
INSERT_UPDATE_FLAG should be either I - Insert or U - Update. |
SB-AR-CUST-10052 |
CUSTOMER_STATUS should be either A - Active or I - Inactive. |
SB-AR-CUST-10053 |
CUSTOMER_TYPE should be either I - Internal or R - External. |
SB-AR-CUST-10054 |
PRIMARY_SITE_USE_FLAG should be either Y - Yes or N - No or NULL. |
SB-AR-CUST-10055 |
BILL_TO_ORIG_ADDRESS_REFP cannot be NULL. |
SB-AR-CUST-10056 |
ORIG_SYSTEM_ADDRESS_REF does not exist in RA_ADDRESSES table. |
SB-AR-CUST-10057 |
ORIG_SYSTEM_CUSTOMER_REF Value should be validated against the RA_CUSTOMERS Table based on Insert_Update_Flag Value. |
SB-AR-CUST-10058 |
CITY,PROVINCE,STATE,COUNTY,POSTAL CODE, and COUNTRY fields should not be null and have valid data when ADDRESS1 is Not Null. |
SB-AR-CUST-10059 |
PRIMARY SITE USE FLAG Should not be null when ADDRESS1 is not null. |
SB-AR-PROFILE-10100 |
INSERT_UPDATE_FLAG is a required column. Enter a valid value. |
SB-AR-PROFILE-10101 |
ORIG_SYSTEM_CUSTOMER_REF is a required column. Enter a valid value. |
SB-AR-PROFILE-10102 |
CREDIT_HOLD is a required column. Enter a valid value. |
SB-AR-PROFILE-10103 |
LAST_UPDATED_BY is a required column. Enter a valid value. |
SB-AR-PROFILE-10104 |
LAST_UPDATE_DATE is a required column. Enter a valid value. |
SB-AR-PROFILE-10105 |
CREATION_DATE is a required column. Enter a valid value. |
SB-AR-PROFILE-10106 |
CREATED_BY is a required column. Enter a valid value. |
SB-AR-PROFILE-10108 |
Valid values for CREDIT_BALANCE_STATEMENTS column are Y,N. |
SB-AR-PROFILE-10109 |
CREDIT_BALANCE_STATEMENTS must be N when STATEMENTS = N.Mandatory when STATEMENTS =Y. Must be null when STATEMENTS is null. |
SB-AR-PROFILE-10111 |
Valid VALUES FOR CREDIT_CHECKING COLUMN are Y,N. |
SB-AR-PROFILE-10112 |
Valid VALUES FOR CREDIT_HOLD COLUMN are Y,N. |
SB-AR-PROFILE-10113 |
Valid VALUES FOR DISCOUNT_TERMS COLUMN are Y,N. |
SB-AR-PROFILE-10114 |
Valid VALUES FOR DUNNING_LETTERS COLUMN are Y,N. |
SB-AR-PROFILE-10115 |
Valid VALUES FOR INTEREST_CHARGES COLUMN are Y,N. |
SB-AR-PROFILE-10116 |
Valid VALUES FOR STATEMENTS COLUMN are Y,N. |
SB-AR-PROFILE-10117 |
Valid VALUES FOR OVERRIDE_TERMS COLUMN are Y,N. |
SB-AR-PROFILE-10118 |
Valid VALUES FOR CHARGE_ON_FINANCE_CHARGE_FLAG COLUMN are Y,N.Required IF INTEREST_CHARGES IS SET TO Y AND no PROFILE class IS specified. |
SB-AR-PROFILE-10120 |
CHARGE_ON_FINANCE_CHARGE_FLAG not required IF INTEREST_CHARGES IS SET TO N OR NULL. |
SB-AR-PROFILE-10121 |
Valid VALUES FOR AUTO_REC_INCL_DISPUTED_FLAG COLUMN are Y,N. |
SB-AR-PROFILE-10122 |
Valid VALUES FOR CONS_INV_FLAG COLUMN are Y,N. |
SB-AR-PROFILE-10123 |
Valid VALUES FOR CONS_INV_TYPE COLUMN are SUMMARY,DETAIL,WHEN CON_INV_FLAG IS Y. |
SB-AR-PROFILE-10124 |
CURRENCY_CODE required IF ANY one OF the following COLUMNS have VALUES. |
SB-AR-PROFILE-10125 |
CURRENCY_CODE does not exist IN TABLE FND_CURRENCIES. |
SB-AR-PROFILE-10126 |
CUSTOMER_PROFILE_CLASS_NAME does not exist IN TABLE HZ_CUST_PROFILE_CLASSES. |
SB-AR-PROFILE-10127 |
IF COLUMN CUSTOMER_PROFILE_CLASS_NAME IS NULL,THEN enter the following COLUMNS COLLECTOR_NAME, CREDIT_BALANCE_STATEMENTS, CREDIT_CHECKING,’ || ’AUTO_REC_INCL_DISPUTED_FLAG, DISCOUNT_TERMS, DUNNING_LETTER, DUNNING_LETTER_SET_NAME, INTEREST_CHARGES, INTEREST_PERIOD_DAYS, CHARGE_ON_FINANCE_CHARGE_FLAG,’ || ’STATEMENTS, STATEMENT_CYCLE_NAME, TOLERANCE, TAX_PRINTING_OPTION, OVERRIDE_TERMS, GROUPING_RULE_NAME, STATEMENTS, CHARGE_ON_FINANCE_CHARGE_FLAG, AUTOCASH_HIERARCHY_NAME. |
SB-AR-PROFILE-10128 |
ACCOUNT_STATUS does not exist IN TABLE AR_LOOKUPS. |
SB-AR-PROFILE-10129 |
AUTOCASH_HIERARCHY_NAME does not exist IN TABLE AR_AUTOCASH_HIERARCHIES. |
SB-AR-PROFILE-10130 |
COLLECTOR_NAME does not exist IN TABLE AR_COLLECTORS. |
SB-AR-PROFILE-10131 |
CREDIT_RATING does not exist IN TABLE AR_LOOKUPS. |
SB-AR-PROFILE-10132 |
DISCOUNT_GRACE_DAYS Must be greater than OR equal TO 0 AND, must be NULL WHEN DISCOUNT_TERMS IS NULL OR No. |
SB-AR-PROFILE-10133 |
DUNNING_LETTER_SET_NAME does not exist IN TABLE AR_DUNNING_LETTER_SETS. |
SB-AR-PROFILE-10134 |
DUNNING_LETTER_SET_NAME mandatory WHEN DUNNING_LETTERS IS Yes.Must be NULL WHEN DUNNING_LETTERS IS No OR NULL. |
SB-AR-PROFILE-10135 |
GROUPING_RULE_NAME does not exist IN TABLE RA_GROUPING_RULES. |
SB-AR-PROFILE-10136 |
INTEREST_PERIOD_DAYS must be greater than OR equal TO zero, mandatory when INTEREST_CHARGES value is Y. Must be NULL when INTEREST_CHARGES value is N OR NULL. |
SB-AR-PROFILE-10137 |
ORIG_SYSTEM_CUSTOMER_REF does not exist IN TABLE RA_CUSTOMERS AND SB_RA_CUSTOMERS_INTERFACE. |
SB-AR-PROFILE-10138 |
ORIG_SYSTEM_ADDRESS_REF does not exist IN TABLE RA_ADDRESSES AND SB_RA_CUSTOMERS_INTERFACE. |
SB-AR-PROFILE-10139 |
TRX_CREDIT_LIMIT AND OVERALL_CREDIT_LIMIT must both be filled IN,OR both be NULL. |
SB-AR-PROFILE-10140 |
RISK_CODE does not exist IN TABLE AR_LOOKUPS. |
SB-AR-PROFILE-10141 |
STANDARD_TERM_NAME does not exist IN TABLE RA_TERMS. |
SB-AR-PROFILE-10142 |
STATEMENT_CYCLE_NAME does not exist IN TABLE AR_STATEMENT_CYCLES. |
SB-AR-PROFILE-10143 |
STATEMENT_CYCLE_NAME must be NULL WHEN STATEMENTS IS No OR NULL. Mandatory WHEN STATEMENTS IS Yes. |
SB-AR-PROFILE-10144 |
TAX_PRINTING_OPTION does not exist IN TABLE AR_LOOKUPS. |
SB-AR-PROFILE-10145 |
CLEARING_DAYS must be greater than OR equal TO zero. |
SB-AR-PROFILE-10146 |
PAYMENT_GRACE_DAYS must be greater than OR equal TO zero. |
SB-AR-PROFILE-10147 |
TOLERANCE must be BETWEEN -100 AND 100. |
SB-AR-PROFILE-10148 |
ORG_ID does not exist IN VIEW HR_ORGANIZATION_UNITS_V. |
This section provides a description of each of the Cash Management error codes.
Table 1–24 Cash Management Errors
Error Code |
Error Message |
---|---|
SB-CE-STHDR-30100 |
STATEMENT_NUMBER is a required column. Enter a valid value. |
SB-CE-STHDR-30101 |
BANK_ACCOUNT_NUM is a required column. Enter a valid value. |
SB-CE-STHDR-30102 |
STATEMENT_DATE is a required column. Enter a valid value. |
SB-CE-STHDR-30103 |
CURRENCY_CODE is a required column. Enter a valid value. |
SB-CE-STHDR-30107 |
CURRENCY_CODE should be the same as the currency code defined for the bank account in AP_Banks_Accounts_All table. |
SB-CE-STHDR-30108 |
CURRENCY_CODE does not exist IN TABLE FND_CURRENCIES. |
SB-CE-STHDR-30109 |
CONTROL_END_BALANCE should be equal to (CONTROL_BEGIN_BALANCE - CONTROL_TOTAL_DR + CONTROL_TOTAL_CR). |
SB-CE-STHDR-30110 |
Valid values for RECORD_STATUS_FLAG column are E,N. |
SB-CE-STHDR-30111 |
BANK_ACCOUNT_NUM does not exist IN TABLE AP_Banks_Accounts_All. |
SB-CE-STHDR-30112 |
BANK_NAME does not exist IN TABLE AP_Bank_Branches. |
SB-CE-STHDR-30113 |
BANK_BRANCH_NAME does not exist IN TABLE AP_Bank_Branches. |
SB-CE-STHDR-30114 |
CHECK_DIGITS does not match with check_digits of the bank account number entered IN TABLE AP_Banks_Accounts_All. |
SB-CE-STHDR-30115 |
ORG_ID does not exist IN view HR_ORGANIZATION_UNITS_V. |
SB-CE-STATE-30200 |
Bank_Account_Num cannot be NULL. |
SB-CE-STATE-30201 |
Statement_Number cannot be NULL. |
SB-CE-STATE-30202 |
Line_number cannot be NULL. |
SB-CE-STATE-30203 |
TRX_DATE cannot be NULL. |
SB-CE-STATE-30204 |
Amount cannot be NULL. |
SB-CE-STATE-30205 |
TRX_CODE cannot be NULL. |
SB-CE-STATE-30210 |
Bank_Account_Num does not exists in SB_CE_STATEMENT_HEAD_INTERFACE. |
SB-CE-STATE-30211 |
Statement_Number does not exists in SB_CE_STATEMENT_HEAD_INTERFACE. |
SB-CE-STATE-30212 |
Currency_code does not exist in FND_CURRENCIES. |
SB-CE-STATE-30220 |
TRX_code does not exist in CE_TRANSACTION_CODES. |
SB-CE-STATE-30221 |
Exchange_rate does not exist in GL_DAILY_RATES. |
SB-CE-STATE-30222 |
Exchange_rate_date does not exist in GL_DAILY_RATES. |
SB-CE-STATE-30223 |
Exchange_rate_type does not exist in GL_DAILY_RATES. |
SB-CE-STATE-30224 |
Trx_date cannot be greater than sysdate. |
SB-CE-STATE-30225 |
Bank_trx_number does not exist in AP_CHECKS_V. |
This section provides a description of each of the Fixed Assets error codes.
Table 1–25 Fixed Assets Errors
Error Code |
Error Message |
---|---|
SB-FA-CATE-50200 |
CATEGORY_ID cannot be NULL. |
SB-FA-CATE-50201 |
SUMMARY_FLAG cannot be NULL. |
SB-FA-CATE-50202 |
ENABLED_FLAG cannot be NULL. |
SB-FA-CATE-50203 |
OWNED_LEASED cannot be NULL. |
SB-FA-CATE-50204 |
LAST_UPDATE_DATE cannot be NULL. |
SB-FA-CATE-50205 |
LAST_UPDATED_BY cannot be NULL. |
SB-FA-CATE-50206 |
CATEGORY_TYPE cannot be NULL. |
SB-FA-CATE-50207 |
CAPITALIZE_FLAG cannot be NULL. |
SB-FA-CATE-50208 |
CAPITALIZE_FLAG should be either YES or NO. |
SB-FA-CATE-50209 |
CATEGORY_TYPE should be in LEASE,LEASEHOLD,IMPROVEMENT,NON-LEASE. |
SB-FA-CATE-50210 |
ENABLED_FLAG should be either Y or N. |
SB-FA-CATE-50211 |
OWNED_LEASED should be either OWNED or LEASED. |
SB-FA-CATE-50212 |
PROPERTY_1245_1250_CODE should be either 1245 or 1250. |
SB-FA-CATE-50213 |
PROPERTY_TYPE_CODE should be either PERSONAL or REAL. |
SB-FA-CATE-50214 |
SUMMARY_FLAG should be either Y or N. |
SB-FA-LOC-50100 |
LOCATION_ID is a required column. Enter a valid value. |
SB-FA-LOC-50101 |
SUMMARY_FLAG is a required column. Enter a valid value. |
SB-FA-LOC-50102 |
ENABLED_FLAG is a required column. Enter a valid value. |
SB-FA-LOC-50104 |
LAST_UPDATED_BY is a required column. Enter a valid value. |
SB-FA-LOC-50105 |
LAST_UPDATE_DATE is a required column. Enter a valid value. |
SB-FA-LOC-50110 |
Valid values for ENABLED_FLAG column are Y,N. |
SB-FA-LOC-50111 |
Valid values for SUMMARY_FLAG column are Y,N. |
SB-FA-MASS-50000 |
ACCOUNTING_DATE cannot be NULL. |
SB-FA-MASS-50001 |
ASSET_CATEGORY_ID cannot be NULL. |
SB-FA-MASS-50002 |
ASSET_TYPE cannot be NULL. |
SB-FA-MASS-50003 |
BOOK_TYPE_CODE cannot be NULL. |
SB-FA-MASS-50004 |
CREATED_BY cannot be NULL. |
SB-FA-MASS-50005 |
CREATED_DATE cannot be NULL. |
SB-FA-MASS-50006 |
DATE_PLACED_IN_SERVICE cannot be NULL. |
SB-FA-MASS-50007 |
DEPRECIATE_FLAG cannot be NULL. |
SB-FA-MASS-50008 |
DESCRIPTION cannot be NULL. |
SB-FA-MASS-50009 |
EXPENSE_CODE_COMBINATION_ID cannot be NULL. |
SB-FA-MASS-50010 |
FIXED_ASSETS_COST cannot be NULL. |
SB-FA-MASS-50011 |
FIXED_ASSETS_UNITS cannot be NULL. |
SB-FA-MASS-50012 |
INVENTORIAL cannot be NULL. |
SB-FA-MASS-50013 |
LAST_UPDATE_DATE cannot be NULL. |
SB-FA-MASS-50014 |
LAST_UPDATE_LOGIN cannot be NULL. |
SB-FA-MASS-50015 |
LAST_UPDATED_BY cannot be NULL. |
SB-FA-MASS-50016 |
LOCATIOD_ID cannot be NULL. |
SB-FA-MASS-50017 |
MASS_ADDITION_ID cannot be NULL. |
SB-FA-MASS-50018 |
PAYABLES_CODE_COMBINATION_ID cannot be NULL. |
SB-FA-MASS-50019 |
PAYABLES_COST cannot be NULL. |
SB-FA-MASS-50020 |
PAYABLES_UNITS cannot be NULL. |
SB-FA-MASS-50021 |
POSTING_STATUS cannot be NULL. |
SB-FA-MASS-50022 |
QUEUE_NAME cannot be NULL. |
SB-FA-MASS-50023 |
AP_DISTRIBUTION_LINE_NUMBER does not exists in AP_INVOICE_DISTRIBUTIONS_ALL table. |
SB-FA-MASS-50024 |
ASSIGNED_TO does not exists in FA_EMPLOYEES table. |
SB-FA-MASS-50025 |
INVOICE_ID does not exists in AP_INVOICES_ALL table. |
SB-FA-MASS-50026 |
ADD_TO_ASSET_ID does not exists in FA_ADDITIONS_B table. |
SB-FA-MASS-50027 |
ASSET_NUMBER does not exists in FA_ADDITIONS_B. |
SB-FA-MASS-50028 |
PARENT_ASSET_ID does not exists in FA_ADDITIONS_B. |
SB-FA-MASS-50029 |
ASSET_KEY_CCID does not exists in FA_ASSET_KEYWORDS. |
SB-FA-MASS-50030 |
BOOK_TYPE_CODE does not exists in FA_BOOK_CONTROLS. |
SB-FA-MASS-50031 |
ASSET_CATEGORY_ID does not exists in FA_CATEGORIES_B. |
SB-FA-MASS-50032 |
LOCATION_ID does not exists in FA_LOCATIONS. |
SB-FA-MASS-50033 |
PARENT_MASS_ADDITION_ID does not exists in FA_MASS_ADDITIONS. |
SB-FA-MASS-50034 |
PAYABLES_CODE_COMBINATION_ID does not exists in GL_CODE_COMBINATIONS. |
SB-FA-MASS-50035 |
EXPENSE_CODE_COMBINATION_ID does not exists in GL_CODE_COMBINATIONS. |
SB-FA-MASS-50036 |
PROJECT_ID does not exists in PA_PROJECTS_ALL. |
SB-FA-MASS-50037 |
PROJECT_ASSET_LINE_ID does not exists in PA_PROJECT_ASSET_LINES_ALL. |
SB-FA-MASS-50038 |
TASK_ID does not exists in PA_TASKS. |
SB-FA-MASS-50039 |
PO_VENDOR_ID does not exists in PO_VENDORS. |
SB-FA-MASS-50040 |
ASSET_TYPE should be either CAPITALIZED, CIP, EXPENSED. |
SB-FA-MASS-50041 |
DEPRECIATE_FLAG should be either YES or NO. |
SB-FA-MASS-50042 |
PAYABLES_UNITS should have same value as that of FIXED_ASSETS_UNITS column. |
SB-FA-MASS-50043 |
POSTING_STATUS should be either NEW, ON HOLD, POST. |
SB-FA-MASS-50044 |
QUEUE_NAME should have same value as that of POSTING_STATUS. |
SB-FA-MASS-50045 |
INVENTORIAL should be either YES or NO. |
SB-FA-MASS-50046 |
NEW_MASTER_FLAG should be either YES or NO. |
SB-FA-MASS-50047 |
SHORT_FISCAL_YEAR_FLAG should be either YES or NO. |
SB-FA-MASS-50048 |
CONVERSION_DATE should not be NULL, when SHORT_FISCAL_YEAR_FLAG is YES. |
This section provides a description of each of the General Ledger error codes.
Table 1–26 General Ledger Errors
Error Code |
Error Message |
---|---|
SB-GL-BUDGT-40000 |
BUDGET_NAME cannot be NULL. |
SB-GL-BUDGT-40001 |
BUDGET_ENTITY_NAME cannot be NULL. |
SB-GL-BUDGT-40002 |
CURRENCY_CODE cannot be NULL. |
SB-GL-BUDGT-40003 |
FISCAL_YEAR cannot be NULL. |
SB-GL-BUDGT-40004 |
UPDATE_LOGIC_TYPE cannot be NULL. |
SB-GL-BUDGT-40005 |
CURRENCY_CODE does not exists in FND_CURRENCIES table. |
SB-GL-BUDGT-40006 |
BUDGET_ENTITY_ID does not exists in GL_BUDGET_ENTITIES table. |
SB-GL-BUDGT-40007 |
BUDGET_VERSION_ID does not exists in GL_BUDGET_VERSIONS table. |
SB-GL-BUDGT-40008 |
CODE_COMBINATION_ID does not exists in GL_CODE_COMBINATIONS table. |
SB-GL-BUDGT-40009 |
PERIOD_TYPE does not exists in GL_PERIOD_TYPES table. |
SB-GL-BUDGT-40010 |
SET_OF_BOOKS_ID does not exists in GL_SETS_OF_BOOKS table. |
SB-GL-BUDGT-40011 |
ACCOUNT_TYPE should be either A-Asset, L-Liability, E-Expense, O-Owners Equity, R-Revenue. |
SB-GL-BUDGT-40012 |
DR_FLAG should be either Y-Yes, N-No. |
SB-GL-BUDGT-40013 |
UPDATE_LOGIC_TYPE should be either A-Add, R-Replace. |
SB-GL-BUDGT-40014 |
BUDGET_ENTITY_NAME does not exists in GL_BUDGET_ENTITIES table. |
SB-GL-BUDGT-40015 |
FISCAL_YEAR does not exists in GL_ENTITY_BUDGETS table. |
SB-GL-DLRT-40100 |
FROM_CURRENCY is a required column. Enter a valid value. |
SB-GL-DLRT-40101 |
TO_CURRENCY is a required column. Enter a valid value. |
SB-GL-DLRT-40102 |
FROM_CONVERSION_DATE is a required column. Enter a valid value. |
SB-GL-DLRT-40103 |
TO_CONVERSION_DATE is a required column. Enter a valid value. |
SB-GL-DLRT-40104 |
USER_CONVERSION_TYPE is a required column. Enter a valid value. |
SB-GL-DLRT-40105 |
CONVERSION_RATE is a required column. Enter a valid value. |
SB-GL-DLRT-40106 |
MODE_FLAG is a required column. Enter a valid value. |
SB-GL-DLRT-40120 |
FROM_CURRENCY does not exist IN TABLE FND_CURRENCIES. |
SB-GL-DLRT-40121 |
TO_CURRENCY does not exist IN TABLE FND_CURRENCIES. |
SB-GL-DLRT-40122 |
USER_ID does not exist IN TABLE FND_USER. |
SB-GL-DLRT-40123 |
USER_CONVERSION_TYPE does not exist IN TABLE GL_DAILY_CONVERSION_TYPES. |
SB-GL-DLRT-40130 |
Valid values for LAUNCH_RATE_CHANGE column are Y,N. |
SB-GL-DLRT-40131 |
Valid values for MODE_FLAG column are D,I,X. |
SB-GL-INTERFACE-40200 |
STATUS cannot be NULL. |
SB-GL-INTERFACE-40201 |
SET_OF_BOOKS_ID cannot be NULL. |
SB-GL-INTERFACE-40202 |
USER_JE_SOURCE_NAME cannot be NULL. |
SB-GL-INTERFACE-40203 |
USER_JE_CATEGORY_NAME cannot be NULL. |
SB-GL-INTERFACE-40204 |
ACCOUNTING_DATE cannot be NULL. |
SB-GL-INTERFACE-40205 |
CURRENCY_CODE cannot be NULL. |
SB-GL-INTERFACE-40206 |
DATE_CREATED cannot be NULL. |
SB-GL-INTERFACE-40207 |
CREATED_BY cannot be NULL. |
SB-GL-INTERFACE-40208 |
ACTUAL_FLAG cannot be NULL. |
SB-GL-INTERFACE-40209 |
SET_OF_BOOKS_ID does not exists in GL_SETS_OF_BOOKS Table. |
SB-GL-INTERFACE-40210 |
CURRENCY_CODE does not exists in FND_CURRENCIES Table. |
SB-GL-INTERFACE-40211 |
FUNCTIONAL_CURRENCY_CODE does not exists in FND_CURRENCIES table. |
SB-GL-INTERFACE-40212 |
BUDGET_VERSION_ID does not exists in GL_BUDGET_VERSIONS table. |
SB-GL-INTERFACE-40213 |
JE_BATCH_ID does not exists in GL_JE_BATCHES table. |
SB-GL-INTERFACE-40214 |
ENCUMBRANCE_TYPE_ID does not exists in GL_ENCUMBRANCE_TYPES table. |
SB-GL-INTERFACE-40215 |
JE_HEADER_ID does not exists in GL_JE_HEADRS table. |
SB-GL-INTERFACE-40216 |
JE_LINE_NUM does not exists in GL_JE_LINES table. |
SB-GL-INTERFACE-40217 |
CODE_COMBINATION_ID does not exists in GL_CODE_COMBINATIONS table. |
SB-GL-INTERFACE-40218 |
ORIGINATING_BAL_SEG_VALUE does not exists in FND_FLEX_VALUES table. |
SB-GL-INTERFACE-40219 |
USER_CURRENCY_CONVERSION_TYPE does not exists in GL_DAILY_CONVERSION_TYPES table. |
SB-GL-INTERFACE-40220 |
USER_JE_CATEGORY_NAME does not exists in GL_JE_CATEGORIES table. |
SB-GL-INTERFACE-40221 |
USER_JE_SOURCE_NAME does not exists in GL_JE_SOURCES table. |
SB-GL-INTERFACE-40222 |
PERIOD_NAME does not exists in GL_PERIODS table. |
SB-GL-INTERFACE-40223 |
USSGL_TRANSACTION_CODE does not exists in GL_USSGL_TRANSACTION_CODES table. |
SB-GL-INTERFACE-40224 |
ACTUAL_FLAG should be either A-Actual, B-Budget, E-Encumbrance. |
SB-GL-INTERFACE-40225 |
AVERAGE_JOURNAL_FLAG should be either Y-Yes, N-No. |
SB-GL-INTERFACE-40226 |
CURRENCY_CONVERSION_RATE should be entered for USER_CURRENCY_CONVERSION_TYPE = User. |
SB-GL-INTERFACE-40227 |
CURRENCY_CONVERSION_DATE should be entered for USER_CURRENCY_CONVERSION_TYPE!= User. |
This section provides configuration information for the PeopleSoft Integration Gateway and Java CAPS postings.
For the Sun Java Composite Application Platform Suite to post and receive messages from PeopleSoft, you must configure the PeopleSoft server. The configurations are different for PeopleTools 8.13 and 8.42. For PeopleTools 8.42, there are also different configurations depending on whether the PeopleSoft adapter Project uses JMS, HTTP, or both. The table summarizes the different configurations.
Table 1–27 Configuration Requirements for PeopleSoft
Version |
JMS |
HTTP |
---|---|---|
PeopleTools 8.42 |
Source node Target node .bindings file IntegrationGateway.properties |
Source node Target node HTTP listening connector HTTP publication handler |
PeopleTools 8.13 |
n/a |
PeopleSoft message node HTTP message node Message channel inbound Message channel outbound PeopleSoft subscription handler HTTP publication handler |
The sections describe how to configure PeopleSoft servers to communicate with the PeopleSoft adapter using PeopleTools 8.42 or 8.13. Information about the PeopleSoft server can be found in the PeopleBooks documentation provided by PeopleSoft.
This section describes how to configure PeopleTools 8.42 to integrate using the Sun Java Composite Application Platform Suite. When you use this version of PeopleTools, you can create the PeopleSoft adapter Projects that use inbound and outbound JMS data flows, and inbound HTTP data flows. Inbound HTTP data flows are only supported when you use an eInsight implementation of the adapter.
The following section describes how to create PeopleSoft nodes to receive and post messages with the Sun Java Composite Application Platform Suite.
The procedure describes how to set up the PeopleSoft node to receive Enterprise Service Bus messages.
Log into the PeopleSoft server.
Follow the PeopleSoft documentation to create a new node and configure it.
Add a transaction for the Enterprise Service Bus post using your own naming convention and configure it.
Click Edit. The Transaction Detail tab appears.
Configure the transaction.
Click Messages. From the Messages tab, configure the messages for the Enterprise Service Bus post.
Each channel must be defined and activated before the adapter can post any data. The procedure describes how to activate the message channels for subscription to the PeopleSoft adapter.
From the PeopleSoft Application Designer, create a channel. You can use the default properties.
Create the request and response message definitions. These message do not require PeopleCode.
Click Message Properties. The Message Properties dialog box appears.
Select the Active option and click OK.
The procedure describes how to create and configure PeopleSoft nodes to post messages to Enterprise Service Bus using HTTP.
Follow the PeopleSoft documentation to create a new node using your own naming convention and configure it.
Select the target connector ID. From the Connectors tab, enter the values displayed in Figure 1–3.
Use the following format for the PRIMARYURL property:
http://<yourmachinename>:18001/<yourdeploymentname>_servlet_<servletname> /<servletname> |
This property must match the logical eWay Servlet-url property defined in the Netbeans IDE . The port number must match the default Web server port number specified in the Integration Server properties in the Enterprise Designer. The Deployment Profile is the name of the Project’s Deployment Profile defined in the Enterprise Designer. The Deployment Profile name must be followed by _servlet_servletname.
Configure the transaction.
Click Edit.
Click Messages. The Messages tab is displayed.
After creating the source node in PeopleTools, follow the procedure to create the JMS target node.
Follow the PeopleSoft documentation to create a new node using your own naming convention and configure it.
Select the target connector ID, and enter the values shown.
The JMS properties, such as persistence and acknowledgement modes, must match the settings for the JMS client as defined from the Connectivity Map. For information about JMS properties, refer to the Java CAPS JMS Reference .
The JMSQueue or JMSTopic property must match the name of the queue/topic in the Connectivity Map. The target destination must match the incoming queue/topic, and the source destination must match the outgoing queue/topic.
The JMSFactory property must point to the topic or queue ConnectionFactory for the topic or queue properties in the JNDI bindings file.
The JMSUrl property must point to your JNDI bindings file (see Creating the JNDI Bindings File for JMS PostingCreating the JNDI Bindings File for JMS Posting).
Make sure that the node that uses JMSTargetConnector as the connector is setup correctly in regard to the, JMSUserName, JMSPassword.
Two types of HTTP connectors are used with PeopleSoft adapter Projects that use HTTP to communicate to PeopleSoft: the HTTP listening connector and the HTTP target connector.
The PeopleSoft server uses the HTTP listening connector to receive messages from. The PeopleSoft adapter HTTP client external application is used to post to the HTTP listening connector. You do not have to configure the HTTP listening connector; the connector is started automatically by the PeopleSoft Integration Application.
However, you must set the location for the HTTP listening connector in the Environment properties of the PeopleSoft Adapter. The routing of messages in the PeopleSoft server is decided by the content of the message in the header section.
The HTTP target connector is used to send HTTP messages to Enterprise Service Bus. The Enterprise Service Bus component receiving the HTTP message is a servlet. The servlet name is specified in the Connectivity Map.
In a text editor, open the web.xml file in the following directory:
bea\wlserv6.1\config\peoplesoft\applications\PSIGN\WEB-INF |
where, bea is the WebLogic installation directory.
Verify that the following section is included, and add it if it is absent.
To configure inbound JMS connections, you must edit the IntegrationGateway.properties file as described in the procedure.
Open the IntegrationGateWay.properties file from the following directory:
bea\wlserver6.1\config\peoplesoft\applications\PSIGW\WEB-INF |
where, bea is the WebLogic installation directory.
Edit the file for the JMS queue listener properties.
You can configure multiple queues by using the convention ig.jms.queue1, ig.jms.queue2, ig.jms.queue3, and so on. Configuring Inbound JMS Connections shows how the JMS listener is configured for the GenericOutQueue.
ig.jms.Queues=1 |
“1” indicates only one queue. |
|
ig.jms.Queue1=GenericOutQueue |
The first queue name “GenericOutQueue”, must be the same in the .bindings file. The Java code used to generate the entry in the .bindings is:
|
|
ig.jms.Queue1.Provider=SunSeeBeyond |
The “SunSeeBeyond” entry must match the configuration entry in the integrationgateway.properties file: ig.jms.JMSProvider.JNDIFactory.SeeBeyond=com.sun.jndi.fscontext.RefFSContextFactory |
|
ig.jms.Queue1.JMSFactory=QueueConnectionFactory |
“QueueConnectionFactory” is the JNDI name in the .bindings file. Use the following Java code to generate the entry:
|
|
ig.jms.Queue1.MessageSelector= | ||
ig.jms.Queue1.Url=file:c:/jndibindings/ |
The URL of the .bindings file. Because PeopleSoft only supports fcontext, this is a directory name. |
|
ig.jms.Queue1.User=Administrator |
User name to Enterprise Service Bus JMS server. |
|
ig.jms.Queue1.Password=SwBAuVVABok= |
Encrypted value of the password to Enterprise Service Bus JMS server. Use the PeopleSoft utility pscipher to get the encrypted value. |
Edit the file for the JMS queue listener properties.
You can configure multiple queues by using the convention ig.topic1, ig.topic2, ig.topic3, and so on. The table shows how to configure the JMS topic to use the GenericOutTopic.
ig.jms.Topics=1 |
“1” indicates only one topic. |
|
ig.jms.Topic1=GenericOutTopic |
The first topic name “GenericOutTopic”, must be the same in the .bindings file. The Java code to generate this entry in the .bindings is:
|
|
ig.jms.Topic1.Provider=SunSeeBeyond |
The “SunSeeBeyond” entry must match the configuration entry in the integrationgateway.properties file: ig.jms.JMSProvider.JNDIFactory.SeeBeyond=com.sun.jndi.fscontext.RefFSContextFactory |
|
ig.jms.Topic1.JMSFactory=TopicConnectionFactory |
“TopicConnectionFactory” is the JNDI name in the .bindings file. Use the following Java code to generate the entry: TopicConnectionFactory tgttcf = null;
|
|
ig.jms.Topic1.MessageSelector= |
Refer to the queue table. |
|
ig.jms.Topic1.Url=file:c:/jndibindings/ |
Refer to the queue table. |
|
ig.jms.Topic1.User=Administrator |
Refer to the queue table. |
|
ig.jms.Topic1.Password=SwBAuVVABok= |
Refer to the queue table. |
To enable the PeopleSoft Adapter to post to PeopleSoft using JMS, you must have a JNDI bindings file in place. You can generate the bindings file with any standard JNDI generation application. Sun provides a sample generation application called PSFTBindJMS.java. This program and two associate applications, compile.bat and run.bat, are included in the sample Project file.
You must edit and recompile the PSFTBindJMS.java file before generating the bindings file.
Create the directory, C:\testprogram. Copy the PSFTBindJMS.java, compile.bat, and run.bat files to this directory.
The latest version of the Enterprise Service Bus API Kit JAR files must be added to the WebLogic PeopleSoft-PIS server classpath. To confirm this, check the JAR files in the server’s setENV.cmd file located in the following location (or equivalent): C:\bea\wlserver6.1\config\peoplesoft\setEnv.cmd If you have installed the PeopleSoft-PIA service as a Windows Service, you must uninstall and reinstall the service by executing unInstallNTServicePIA.cmd first, then executing installNTServicePIA.cmd. This is a runtime classpath requirement to confirm the new classpath.
Open the PSFTBindJMS.java file in a text editor and follow the directions presented in the text of the file. Edit the JNDI bindings generation application with the Enterprise Service Bus host name and location. Verify that the Enterprise Service Bus JMS server port number is correct. This port number must match the Server port property for the JMS IQ Manager in the Enterprise Designer. For information, refer to the Java CAPS JMS Reference .
Modify the following line to point to your own directory:
fcontextprops.put(Context.PROVIDER_URL, "file:C:\\eGateExports\\PeopleSoft\\JMS"); |
If you are installing the Sun Java Composite Application Platform Suite and the PeopleSoft Adapter on a computer that previously included ICAN 5.0.5, be sure to delete all of the previously installed API JAR files, and follow the directions in the Sun Enterprise Service Bus API Kit Developer’s Guide to modify your classpath to include the new API JAR files.
Double-click compile.bat to compile the program. A class file is generated.
Double-click run.bat to run the program. This creates a .bindings file.
Copy the .bindings file to the location of the JMSUrl property described in the section above (see Creating Target Nodes to Post to Enterprise Service Bus Using JMS.
When you run the bindings generation application for the first time, the following message is displayed:
fcontext TopicConnectionFactory lookup exception, you never had this jndi entry fcontext TopicConnectionFactory lookup is null... will bind to the jndi name fcontext GenericInTopic lookup exception, it doesn’t exist GenericInTopic is null...bind GenericInTopic as GenericInTopic fcontext GenericOutTopic lookup exception, it doesn’t exist GenericOutTopic is null...bind GenericOutTopic as GenericOutTopic fcontext ErrorTopic lookup exception, it doesn’t exist t is null...bind ErrorTopic as ErrorTopic fcontext QueueConnectionFactory lookup exception it doesn’t exist fcontext QueueConnectionFactory lookup is null...bind with new value fcontext GenericInQueue lookup exception, it doesn’t exist GenericInQueue is null...bind GenericInQueue as GenericInQueue fcontext GenericOutQueue lookup exception GenericOutQueue is null...bind GenericOutQueue as GenericOutQueue |
In the subsequent runs, the following message is displayed:
fcontext TopicConnectionFactory is NOT null...unbind then re-bind TopicConnectionFactory will overwrite old value com.stc.jms.client.STCTopic fcontext GenericInTopic is NOT null...unbind then re-bind GenericInTopic will overwrite old valuecom.stc.jms.client.STCTopic fcontext GenericOutTopic is NOT null...unbind then re-bind GenericOutTopic will overwrite old valuecom.stc.jms.client.STCTopic fcontext ErrorTopic is NOT null...unbind then re-bind ErrorTopic will overwrite old value fcontext QueueConnectionFactory is NOT null...unbind then re-bind QueueConnectionFactorycom.stc.jms.client.STCQueue fcontext GenericInQueue is NOT null...unbind then re-bind GenericInQueue will overwrite old valuecom.stc.jms.client.STCQueue fcontext GenericOutQueue is NOT null...unbind then re-bind GenericOutQueue will overwrite old value |
Once you have completed all of these steps, restart the PeopleSoft-PIA services. You can restart the PIA services from the Windows Services console, or you can restart the service from a Command Line using the following command:
startIA.cmd |
After you execute this command, monitor the PIA_weblogic.log file until you see the following output:
#### <> <000329> |
This indicates that the PIA Service is started. If you use this method of starting the PIA service, be aware that the Windows Services console will not accurately reflect that the service has been started.
Stop and restart the JMSListeningConnector using the URL (see Starting and Stopping the JMS Listening Connector). After you start the JMS Listening Connector, monitor the PIA_weblogic.log. The following message indicates that the JMS Listening Connector has started correctly:
#### <> <> <101047> <[WebAppServletContext(2244929,PSIGW, /PSIGW)] JMSListeningConnectorAdministrator: init> #### <> <> <101047> <[WebAppServletContext(2244929,PSIGW, /PSIGW)] PeopleSoftListeningConnector: init> |
If you perform step Creating the JNDI Bindings File for JMS Posting before the PIA service is ready, the JMS Listening Connector will not be active, so it will not receive messages from Enterprise Service Bus.
To Start the JMS Listening Connector, use the following command:
http://hostname:port/PSIGW/JMSListeningConnectorAdministrator?Activity=START |
To Stop the JMS Listening Connector, use the following command:
http://hostname:port/PSIGW/JMSListeningConnectorAdministrator?Activity=STOP |
To verify if your JMS connection works, you can use the StartSendMaster.bat provided by PeopleSoft in the following location:
c:\bea\wlserver6.1\config\peoplesoft\applications\PSIGW |
You can verify log information for the PeopleSoft server in the following directory:
bea\wlserver6.1\config\peoplesoft\applications\PSIGW |
where bea is the installation directory where WebLogic is installed.
If the Logical Host is shut down during a JMS session with PeopleSoft, the PeopleSoft server looses the session. You must reestablish the connection on the PeopleSoft server.
This section describes how to configure PeopleTools 8.13 to integrate using the Enterprise Service Bus. When you use this version of PeopleTools, you can create PeopleSoft Adapter Projects that use inbound HTTP Collaborations. Outbound HTTP Collaborations are only supported when you use eInsight together with Enterprise Service Bus.
The procedure describes how to create and configure PeopleSoft nodes for Enterprise Service Bus HTTP posting.
In the PeopleTools Application Designer, click New on the File menu. The New dialog box appears.
Click Message Node and click OK to display the Message Node dialog box for Node 1.
Right-click the Locations pane and click Insert Location. The Location dialog box appears.
Enter the URL for the PeopleSoft Gateway Servlet and click OK.
For Apache:
http://PSFTHOST/servlets/psft.pt8.gateway.GatewayServlet |
For WebLogic:
http://PSFTHOST/servlets/gateway |
where PSFTHOST is the name of the host computer where PeopleSoft runs.
The URL name displays in the Message Node dialog box similar to Figure 1–7.
Click Save As on the File menu.
Enter the name of the message node.
From the File menu, click Open. The Open Object window appears.
To verify that the message node is ready for use, select Message Node from the Object Type list and click Open.
A list of all message nodes displays.. The name of the new message node appears in the Objects matching selection criteria pane.
Message nodes with PSFT prefixes are created by the PeopleSoft installation. PSFT_EP is the PeopleSoft local node for the Financials application. It is specified as a subscriber to messages sent from the PeopleSoft Adapter, and a publisher of messages to the HTTP server.
PeopleSoft comes with a set of predefined message definitions. The desired message definition is configurable in the adapter with the Subject property. The following instructions describe how to activate the message definition for subscription to the PeopleSoft Adapter.
For purposes of this publication the ADVANCED_SHIPPING_RECEIPT Message Definition is activated for publish / subscribe.
Each message used for publication must be defined. This definition corresponds to the XML message the adapter publishes, and contains the elements of the data to be published. However, before the Adapter can publish any data, the message definition must be activated. The Application Designer includes a list of these definitions.
In PeopleTools Application Designer, click Open on File menu. The Open Object dialog box appears.
Click Message from the Object Type list. This displays all available PeopleSoft message definitions.
Double-click the message definition. The Message window appears, displaying the record details of the chosen message structure.
Click Object Properties on the File menu,. The Message Properties dialog box appears.
Click the Use tab.
Select the Active option and click OK.
Save your current changes. You have now activated the message definition for publishing or subscribing.
This procedure describes how to configure message channels. Before you start, determine which message channel you will use. You can configure the PeopleSoft Adapter for this message channel with the Channel property.
Each message channel logically groups messages together. For purposes of the procedure, the ADVANCED_SHIPPING_RECEIPT message is grouped into the ADVANCED_SHIPPING_NOTICE message channel.
Log into the PeopleTools Application Designer.
Click Open on the File menu. The Open Object dialog box appears.
Select Message Channel from the Object Type list and click Open. This displays all available message channels.
Double-click the message channel to be used. The Message Channel window appears for that channel.
Click Routing Rules, right-click the pane, and from the shortcut menu, click Insert message node. The Insert Message Node dialog box appears, displaying the available message nodes.
Select PSFT_EP and click Insert. This inserts the message into the routing rules table.
Select STCPUBLISHER and click Insert.
Click Cancel to close the dialog box.
The message nodes are now defined on the Routing Rules tab of the Message Channel window.
Routing directions provide you with the ability to assign destinations (Publish To/Subscribe From) to a message node. This section describes the procedure for defining the routing directions for the adapter message node, Subscribe From.
In the Routing Rules Tab of Message Channel window in the Application Designer, right-click Both (Publish and Subscribe) for STCPUBLISHER, click Routing Direction, then Subscribe From.
Right-click Both (Publish and Subscribe) for PSFT_EP, click Routing Direction, and click Publish To.
The Routing Rules tab now shows that the adapter message node is subscribing to messages from PSFT_EP and is publishing to STCHTTP.
Click Save on the File menu. You have now defined the routing rule that allows the appropriate message to be published from the adapter to PeopleSoft.
The procedure describes how to add the PeopleSoft subscription handler. Before you start the procedure, make a note of the following PeopleSoft configurations:
Jolt listener host
Jolt listener port
PeopleTools version
Operator ID
Operator ID password
Navigate to the following URL in a browser to open the handler directory:
For Apache:
http://PSFTHOST/servlets/psft.pt8config.ConfigServlet |
For WebLogic:
http://PSFTHOST/servlets/gateway.administration |
where PSFTHOST is the host where the PeopleSoft Application Messaging Gateway is installed.
The Handler Directory page appears.
Click Add handler. The Add Handler page appears.
Enter the PeopleSoft handler class:
psft.pt8.psfthandler.PeopleSoftHandler |
and click Save.
Click Load to load the PeopleSoft handler class you just added. The status changes to Loaded successfully.
Click Configure to configure the handler. The Manage Lookup Table page for the PeopleSoft handler appears.
Click Add a new node to associate the node with this subscription handler. The Add an address window appears.
Enter the values for the new node, PSFT_EP, associated with the subscription handler. These values are mandatory.
Click Save address. The Manage Lookup Table page now displays the new node.
The Application Messaging Gateway is now ready to receive XML messages from the adapter and publish the XML messages to PeopleSoft.
To configure PeopleSoft to publish XML messages to the PeopleSoft Adapter involves the following steps:
Refer to Creating the PeopleSoft Node to Receive Enterprise Service Bus HTTP Posts to create a message node associated with the PeopleSoft Adapter. A message node called STCHTTP is used as an example.
Refer to Activating the Message Definition to Receive Enterprise Service Bus Posts to activate the message to be published to the PeopleSoft Adapter. In this case, activate the PO-EXPECTED_RECEIPT_SHIPTO message.
Refer to Defining Message Channel Routing Rules to define the routing rules for the message channel to be used.
Insert the PSFT_EP message node and the HTTP message node previously created.
Define the routing direction. Select Subscribe From for PSFT_EP and Publish To for the HTTP message node (STCHTTP).
This procedure describes how to add the HTTP publication handler. Before you start, verify that the HTTP publication handler is installed. Also, obtain the HTTP configuration values for the adapter which is to receive the XML message(s) from PeopleSoft. These are required when configuring the message node corresponding to the subscription handler.
Navigate to the following URL in a browser to open the handler directory:
For Apache:
http://<yourmachinename>:18001/<yourdeploymentname> _servlet_<servletname>/<servletname>. |
For WebLogic:
http://<PSFTHOST>/servlets/gateway.administration |
where, <PSFTHOST> is the host where the PeopleSoft Application Messaging Gateway is installed.
The Handler Directory page appears.
Click Add handler. The Add Handler page appears.
Enter the HTTP publication handler class and click Save.
com.stc.ewpsoft8.stchttphandler.HTTPHandler |
Click Save. The Handler Directory page displays the new handler.
Click Load. The status changes to Loaded successfully.
Click Configure for the HTTP handler. The HTTP Handler Directory page appears.
Click Add an HTTP node to associate a node with this subscription handler.
Enter the values for the new node associated with the subscription handler. Scroll to the right to access additional columns.
In the Include Headers column, indicate whether or not you want header information to be retained in the received messages. All values are mandatory.
Selecting the check box preserves the header information.
Deselecting the check box strips the header information.
Click Save. This displays the STCHTTP node entries. If the entries are correct, the Application Messaging Gateway now can receive XML messages from PeopleSoft and publish the XML messages to the PeopleSoft Adapter (in HTTP mode).
You can now ping the HTTP host from the system where the com.stc.eWays.psofthandler.jar file is installed. You may need to use the system’s full host name.
When used with alias queues and remote queues, the WebSphere MQ Adapter functions with several restrictions.
Alias queues and remote queues with local queue definitions may be accessed in the same way as actual local queues, through the use of the Adapter OTD’s accessQueue(String) method. Remote queues without local queue definitions need to use the accessQueue(String, String) method instead.
Also, when alias queues or remote queues are used, the Adapter cannot proactively verify the connection (and reconnect, if necessary) before each OTD operation. This is because the Adapter verifies connections by querying queue objects, and it is not possible to query alias queues and remote queues. This means that when alias queues or remote queues are used with the Adapter, the Collaboration is responsible for recovering connection failures itself, including reestablishing the queue manager and queue connections as needed.
For more information, refer to the WebSphere MQ Adapter Javadoc.
When an Adapter connects to a local queue manager and accesses one of its queues, that queue is a local queue. When an Adapter connects to a remote queue manager and accesses one of its queues, then that queue, is also a local queue. In WebSphere MQ terms, a remote queue is a queue that is managed by a queue manager other than the one to which the application (in this case, the Adapter) is connected.
For example, say that there are two queue managers, QM1 and QM2. QM1 manages a queue (Q1) and runs on Host1. QM2 manages a queue (Q2) and runs on Host2.
Furthermore, say that need to send messages to Q2, but the Adapter may only communicate with Host1 (that is, Host2 is unreachable from the system in which the Adapter is executing). By creating the appropriate channels and a remote queue definition (R1 on QM1), messages sent to R1 can be shuttled automatically to Q2 on QM2.
For this example, the Queues and the Adapter are configured as follows:
If either QM1 or QM2 do not have a transmission queue defined, create one. Both queue managers require one transmission queue each. In this example, assume that both queue managers have the transmission queue ’xmit’.
Create a Sender Channel for QM1 that points to Host2 and transmission queue xmit. The name of the channel must match the Receiver Channel created in the next step.
Create a Receiver Channel for Q2. The name of the channel must match the Sender Channel created in the previous step.
In QM1, create a Remote Queue Definition (R1). Designate Q2 as its remote queue, QM2 as its remote queue manager, and xmit as its transmission queue.
Configure the MQ Adapter to connect to Host1, QM1, and have it put messages into queue R1.
Messages cannot be read/GET from remote queues, only PUT. In the example situation above, to read the messages placed in QM2:Q2 through R1, an Adapter needs to connect directly to QM2 (Host2), thereby interacting with Q2 as a local queue.
The first step in creating the sample Project is to install and configure IBM’s WebSphere MQ Server and MQ queue manager on the local host.
It is assumed that the reader is experienced in the use of the WebSphere MQ queue manager. For the sample implementation, perform the following:
Open IBM WebSphere MQ Explorer.
Create a new queue manager.
From the WebSphere MQ queue manager create a new queue.
When using the WebSphere MQ queue manager on UNIX, you must be a member of the mqm group to create and start the MQ queue manager.
It is essential that the WebSphere MQ Administrator regularly monitor the number of messages in the queue. Message expiration settings should be set to allow for extended storage.
WebSphere MQ is limited in the number of messages that can be sent before a commit is executed, and the number of physical messages that can exist on the queue at any one time. This can result in exception errors when upper limits for these numbers are exceeded. Memory and performance of the specific server may also effect the results.