Product Schedule: ibSphere wizard
Draft for approval. Do not use for binding orders or approved customer deliveries. Complete open fields before use; legal and commercial review is required.
1. Product and functions requiring approval
ibSphere wizard supports adjustments to SAP Business One interfaces and workflows. The partner presentation describes capabilities including moving, hiding and renaming fields, required-field and validation rules, additional buttons, macros and Service Layer workflows. Only functions expressly approved for the ordered build form part of the contract.
Complete before ordering: version/build [_____]; standalone product or suite component [_____]; included modules [_____]; read/write actions [_____]; limits for customer-specific scripts [_____]; supported SAP versions, databases and clients [_____]; installation and permission requirements [_____]. Standalone product and licence approval remains to be confirmed.
2. Licence and delivery
The order specifies a perpetual licence or subscription. The licence schedule must state the user, company, instance and test-system scope and SAP system number. The wizard project must implement and verify post-purchase download and ten-day interim licensing, full licensing, system changes and technical expiry controls before that service is sold.
3. Responsibility for configurations
Customer-specific rules, macros and write access must be tested in a suitable test environment for business effect, permissions and data integrity before production use. The customer documents its configurations and maintains backups. Inceptum remains responsible for its services under the agreed terms and applicable law; these cooperation duties do not exclude responsibility for product defects. Individual implementation and customisations require separate commissioning.
4. Operation, data and support
Data flows, external services, telemetry, licence validation and stored configurations must be described for the approved build. No unverified local-only processing or unrestricted platform compatibility is promised. Binding support start and end [_____]; update route [_____]; security contact and reporting process [_____]; data access following licence expiry [_____]; actual third-party notices/SBOM [_____].