The following control maintenance record belongs to the IDMS area in the B2B (Business-to-Business) category.
Indicate whether the system archives IDMS-XML transactions. This control maintenance record is recommended for sites that use the IDMS-XML system very heavily and do not have the system resources (disk space) to store every transaction the system processes.
Allows users to override the A/P branch used on inbound invoices. If this is left control maintenance record is left blank, the inbound invoices default to use the G/L branch of the P/O that is being invoiced.
When processing SalesOrderSubmit transactions, the system requires a G/L account to use as the sales source for the new order. Use this control maintenance record defines which G/L account to use for the sales source of new orders coming into the system through IDMS-XML.
Allows users to specify if the system should disregard discrepancies in the part numbers, units-of-measure, and quantities when checking the validity of inbound invoices.
Allows users to specify an Eclipse user ID or user group that receives messages generated by the IDMS-XML inbound invoicing system. When the system receives invoices from the vendors, any issues in processing the invoices that the system encounters are sent to the user or group specified by this control maintenance record.
When the system determines product availability to display to a specific customer, it first determines which branch’s inventory to include in the displayed quantity available. This control record allows the user to specify which branches a customer’s availability display includes. Valid choices include: “Ship Branch”, “Home Territory”, “Auth Branches”, and “All Branches”. The branches included in the first three of these choices are all defined in Customer Maintenance.
When processing SalesOrderSubmit transactions, when a product being requested that the system cannot identify, indicate how the system should handle creating the item:
If this control maintenance record is blank, then the order creation request fails and returns an error requesting item creation through the IDMS-XML SalesOrderSubmitResponse. The Eclipse system does not create an order.
If this control maintenance record is populated, then the system adds a nonstock item to the order, using the product defined by this control maintenance record as a template, and the system continues processing the order.
Allows users to specify a default user ID to be used when completing the Writer field of new sales orders. If a SalesOrderSubmit transaction comes into the system and does not populate the Writer tag, then the system uses the value from this control maintenance record instead.
Select which items for which you want to display availability in your XML responses: Ship Branch, Home Territory, Auth Branches, All Branches.
New in Release 9.0.4
Indicate if you want the Vantiv-hosted (Element) credit card page embedded in an inline iFrame.
Indicate if you want to return the document type definition (DTD) in your responses. For example, set to No, the system eliminates the following line in the transaction response: <!DOCTYPE IDMS-XML SYSTEM "http://www.eclipseinc.com/dtd/IDMS-XML.dtd"> .
Indicate if you want inbound sales orders to use always use partner pricing rather than use what is assigned in the Eclipse system.
New in Release 9.0.1, Updated Release 9.0.4
Select the Document Image Profile you want to use for the order image based on your settings in Document Profile Maintenance.
Note: This control maintenance record is only used when attaching an actual file and not for queries.
As of Release 9.0.4, this control maintenance record serves as a default if no profile is identified in the XML.
Enter the routines (programs) used to process the various inbound transaction requests.
Important: This control maintenance record is populated during installation and we recommend only experienced programmers manage it.
Allows users to specify how long IDMS-XML sessions remain valid. After the specified number of minutes has elapsed in which a particular SessionID has not been used, this SessionID deletes from the system and invalidates the session. This process then requires the user to log in again. If left blank, the default is thirty (30) minutes.
Enter the valid ship vias to use when creating new orders through the XML routines.
A base-level, global setting for Web Integration/IDMS-XML that enables the Display Availability by Branch in the ProductInquiry and MassProductInquiry XML responses.
This control maintenance record works in conjunction with the IDMS-XML Display Availability For control maintenance record selections. Both control maintenance records act as the global, site-level settings. The Show Availability for Branches setting in the Customer Maintenance > Remote Order Entry Parameter options overrides this control maintenance record.
Enter the login and password to set at the global level for the company as a whole. This allows all users to login and transactions to be processed without having to have users log in.
Allows users to specify the URL to the local xPost servlet. If the Eclipse xServ and xPost servlets are installed on the system, then this control maintenance record must be populated with a URL that the Eclipse system can use to access the xPost servlet residing on the system’s web server.
Important: This control maintenance record is populated during installation and we recommend only experienced programmers manage it.
Enter the user-defined routines (programs) used to process the various inbound transaction requests.
Important: This control maintenance record is populated during installation and we recommend only experienced programmers manage it.
Enter the valid statuses allowed for the IDMS-XML order creation process.
New in Release 9.0.2
See B2B in this documentation.
Allows users to specify a contact to use as a template when creating new contacts through the IDMS-XML system. Populate this control maintenance record with an existing “dummy” contact template in the Eclipse system. All the data fields that Eclipse stores for contacts in its system that are not made available in the Contact tag can be set to default values using this template contact.
Allows users to specify a contact to use as a template when creating new customers through the IDMS-XML system. Populate this control maintenance record with an existing “dummy” customer template in the Eclipse system. All the data fields that Eclipse stores for customers in its system that are not made available in the Entity tag can be set to default values using this template customer.
Allows users to specify a product to use as a template when creating new products through the IDMS-XML system. Populate this control maintenance record with an existing “dummy” product template in the Eclipse system. All the data fields that Eclipse stores for customers in its system that are not made available in the Entity tag can be set to default values using this template customer.
Allows the user to specify the actual text used to describe the various order statuses that the Eclipse system uses to describe orders in the OpenOrderInquiryResponse tag. For the four available order statuses, any text may be used to describe them.