| Installing Upgrading Designing Configuring Deploying Monitoring Administering Troubleshooting Reference JBI Components | |
| Close Print View | |
| Designing: COUNT |
|
Creating a Runtime Environment
Designing Business Processes in the Sun Business Process Manager
Working with TCP/IP HL7 Collaborations
Developing Sun Master Indexes (Repository)
Developing Sun Master Patient Indexes
Developing OTDs for Application Adapters
Date and Time Stamp Requirements
Creating a SAP ALE OTDs Wizard
SAP JCo and SAP IDoc Class Library Installation
Exporting the IDOC File from SAP
Saving the IDoc Description File (After 4.6)
Creating an Oracle Applications OTD
Select Oracle Applications Module
Exposed Oracle Applications OTD Nodes
SWIFT Alliance Gateway Adapter OTD Features
Generating DTDs from PeopleTools 8.13
Generating and Publishing an XML Test Message
To generate a PeopleSoft XML message
Extracting and Viewing the XML Test Message
Generating a DTD for the XML File
OTD Methods and Business Process Operations
Developing OTDs for Communication Adapters
Developing OTDs for Database Adapters
Developing OTDs for Web Server Adapters
Designing with Application Adapters
Designing with Communication Adapters
Designing with Web Server Adapters
Designing with Sun JCA Adapters
Stored procedures for both the OTD level and the interface tables level are defined in the utility package.
If it is located at the OTD root level, the data is counted from all Staging Tables.
If it is located at the Staging Table level, the data is counted only for that specific Staging Table.
Depends upon specific implementation. Typically, it contains at least four input VARCHAR parameters corresponding to:
sb_eway_id
sb_group_id
sb_object_id
Note - If you do not assign a value (including the null value) to the above parameters, the procedure acts on all associated records.
sb_pass_or_fail
This parameter accepts the following values:
P- records that have passed
F- for records that have failed
I- all records
The stored procedure name is derived from the Open Interface name or the Staging Table name, according to the following convention:
At the root level:
If the OPEN_INTERFACE tab has a Util_Name attribute, then this value is used: FN_CNT_<UTILNAME>. Otherwise, the value of the attribute Name is used: FN_CNT_<Open_Interface_Name>.
For example:
Customer Item: FN_CNT_CUSTITEMS
Item Import: FN_CNT_ITEM_IMPORT
At the staging table level:
If the Interface_Table tag has a Util_Name attribute, then this value is used: FN_CNT_<UTILNAME>. Otherwise, the short name of the Name attribute is used: FN_CNT_<Short_Table_Name>.
For example:
Customer Item: FN_CNT_MTL_CI_INTERFACE_INT
Item Import: FN_CNT_MTL_SYSTEM_ITEMS_INT