A channel application for all administrative tasks, including organization management, channel management, catalog management, content management, etc.
The term back office is valid until Enfinity Suite 6. For Intershop 7/Intershop Commerce Management, use the specific management tool name, like Commerce Management.
|backlog||An accumulation over time of work waiting to be done.|
A bank account is a financial account with a banking institution, recording the financial transactions between a person (customer) or a company (client) and the bank.
A bank account will be identified by
|bank identifier code|
The BIC code (also known as SWIFT-BIC, SWIFT ID or SWIFT code) is a standard format of Bank Identifier Codes approved by the International Organization for Standardization (ISO). It is the unique identification code of a particular bank. These codes are used when transferring money between banks, particularly for international wire transfers, and also for the exchange of other messages between banks. The codes can sometimes be found on account statements.
There are two types of BIC: 8 character BIC (also called "BIC8") and 11 character BIC ("BIC11"). A BIC8 identifies a financial institution in a country or a location. A BIC11 identifies the financial institution’s branch.
The structure of an 8 character BIC: bank code, country code, location code
The structure of an 11 character BIC:
|baselining||in Enfinity Suite 6's CMC, the process of first merging a content asset version of an outdated edition with the root edition and then removing the outdated edition|
|basket||see shopping cart|
|basket calculation framework||The basket calculation framework of Intershop 7/Intershop Commerce Management is a framework that covers all tasks required when calculating baskets (shopping carts) or orders. The idea behind this framework is the spreadsheet functionality - values are stored in cells, and you can define rules to be executed once a required value is available.||Overview - Basket Calculation|
|batch process||Generally, batch processing is execution of a series of programs ("jobs") on a computer without manual intervention. In bundled processing of mass data. , it refers to the||Overview - Administration and Configuration|
|bid history||container that saves all changes and states that bids adopted during an auction|
|black box test||Black-box testing is a method of software testing that tests the functionality of an application as opposed to its internal structures or workings (see white box test).|
Specific knowledge of the application's code/internal structure and programming knowledge in general is not required. Test cases are built around specifications and requirements, i.e., what the application is supposed to do. It uses external descriptions of the software, including specifications, requirements, and designs to derive test cases. These tests can be functional or non-functional. The test designer selects valid and invalid inputs and determines the correct output. There is no knowledge of the test object's internal structure.
|bonus card||A bonus card, loyalty card, rewards card, points card, advantage card, or club card is a plastic or paper card, visually similar to a credit card or debit card, that identifies the card holder as a member in a loyalty program. Loyalty cards are a system of the loyalty business model.|
In Enfinity Suite 6, a product pricing means to complement marketing activities in the consumer channel - consumers can collect bonus points granted for products and then redeem them for other products. With bonus points, each product defines a bonus point value and a bonus point price.
Generally, bonus points are a part of loyalty programs. The consumer can collect bonus points under certain conditions defined by the client.
The precondition to collect bonus points have to be considered. That could be:
The influence of returns or order cancellation on the collected bonus points have to be considered.
|bonus point price||in product pricing, the parameter that specifies how many bonus points a user needs to redeem in order to buy this product|
|bonus point value||in product pricing, the parameter that determines how many bonus points a user will earn when buying this product|
Generally, bootstrap (or "bootstrapping") can refer to any process where a simple system activates a more complicated system, used in computing, linguistics, physics, biology, electronics, statistics, finance, etc., see http://en.wikipedia.org/wiki/Bootstrapping_(disambiguation).
In the context of Intershop 7/Intershop Commerce Management, two concepts are relevant:
In a source code management system, a branch is the duplication of an object (such as a source code file, or a directory tree) so that modifications can happen without interfering with the originating branch ("parent" branch).
Branching generally implies the ability to later merge or integrate changes back onto the parent branch.
For specific purposes, there can be feature branches or stabilization branches.
|branding package||Logos, colors and other settings that define the look and feel of a channel application (see application branding)|
Generally, a means to define spending limits for users or certain parts of an organization within a definable time frame.
In Intershop 7/Intershop Commerce Management, promotions can be assigned a budget, which if spent takes the promotion offline regardless of other settings.
|budget violation||the fact of exceeding a given budget amount|
Depending on the context, "build" may refer to
|Overview - Build, Assembly and Deployment|
The process of converting ("compiling") source code into executable software.
In the Intershop 7 context, several build process types were employed (up to Intershop 7.4):
Beginning with the continuous integration support for Intershop 7 and Intershop Commerce Management, Intershop replaces this approach with
|Overview - Build, Assembly and Deployment|
|build server||In software engineering, a build server is a machine on which a software project can be continuously built from changes changes to code artifacts that are committed to the VCS.||Overview - Build, Assembly and Deployment|
|business activity||A business activity is one workflow sequence of a business use case. It reflects a business concept and can cover different system use cases. A particular business activity can be performed in the context of multiple business use cases, like, for example, the BA "log in customer".|
|business address||A business address is an address of a business office or a company.|
Up to Enfinity Suite 6.4, a pre-defined channel type that enables sales organizations and partners to offer goods and services to business customer organizations, to interact with business customer organizations and to receive orders from them.
This concept has become obsolete with Intershop 7.
|business channel management plug-in||The business channel component within the sales organization back office, used by administrators of the parent organization that hosts the business channel. This plug-in allows for managing customers, channel catalogs and products, content and orders.|
In Intershop 7/Intershop Commerce Management, a customer type that represents a business. As opposed to individual customers, business customers
|business intelligence||Business intelligence (BI) refers to skills, technologies, applications and practices used to help a business acquire a better understanding of its commercial context. Business intelligence may also refer to the collected information itself.|
BI applications provide historical, current, and predictive views of business operations. Common functions of business intelligence applications are reporting, analytics, data mining, business performance management, benchmarks, text mining, and predictive analytics.
|Overview - Intershop Commerce Insight (ICI)|
Generally, the logical representation of an entity of the real world. From a developer's perspective, a business object (a.k.a. "domain object") represents a logic entity in a given domain, including attributes, relationships, business rules/logic, policies and constraints.
See business object layer.
|Overview - Business Object Layer|
|business object layer|
The business object layer provides an explicit business-oriented domain model as an API. In a picture that shows the typical architecture layers of a business application, it can be located on top of the persistence layer (or data layer), and below the application layer that forms the actual application from a reusable domain layer - the business object layer.
It forms a new level of abstraction over the persistent state of objects. It comes with concepts to change and extend the behavior of business objects without breaking the cartridge API barrier. It hides the underlying internal implementation, which can still be based on the existing ORM model, or on any other back end. It also provides a more object-oriented view on the available business functionality, which, for example, makes user interface development much easier.
|Overview - Business Object Layer|
|business partner||A business partner is an actor (a person or a company) who initiates actively a business use case or is involved to perform the business use case or a part of it.|
|business process||Generally, a business process is a collection of related, structured business activities that produce a specific result (serve a particular goal) required to reach the (e-commerce) company's business goals. It is a bracket for different business use cases related to the same topic, like order management, product management or fulfillment.|
|business relation||In the procurement business model, relations established between buying organizations and suppliers to allow the buying organization to access and order from supplier catalogs.|
|business role||A business role reflects a group of persons performing the same business activities of a business use case.|
Up to Enfinity Suite 6.4, a front-end channel application of the business channel, used by administrators and buyers of customer organizations. The business storefront allows for organization management, requisition approval, product search and comparison, and requisition and order tracking.
This concept has become obsolete with Intershop 7.
|business tracking||Business tracking is a framework that collects and provides event data for defined events to third party applications (web analytics engines and recommendation engines, which collect data, generate reports and present the results). The business tracking framework defines events that can be triggered, provides components to developers, and offers interfaces and managers for web analytics engines or recommendation engines respectively.||Overview - Business Tracking|
|business use case||As opposed to the system use case, the business use case describes a business sequence (as part of a business process), which is triggered by an active business actor and which generally results in a benefit from the business point of view.|
In management, business value is an informal term that includes all forms of value that determine the health and well-being of the firm. Business value expands concept of value of the firm beyond economic value to include other forms of value such as customer value, supplier value, partner value, and managerial value. Many of these forms of value are not directly measured in monetary terms.
Intershop produces business value by delivering:
|buyer||In B2B scenarios, a buyer represents a user role of a business customer with the permission to create orders.|
|buyer catalog||catalog made available to the buyers in a buying organization|
|buyer template attribute||an item (i.e., a topic) in RFQ template questionnaires to be completed by the buyer|
|buying organization||Enfinity Suite 6 actor that represents a self-contained business organization acting on the buy-side of the procurement model|
|buying organization front end||A front-end channel application of the procurement channel, used by all users of buying organizations, regardless of their particular role (administrator, approver, buyer, order manager.) Depending on the role, the buying organization front end allows for managing the organization, products and catalogs, approval workflows and budget escalations, requisitions, and auctions and RFQs.|
The information provided in the Knowledge Base may not be applicable to all systems and situations. Intershop Communications will not be liable to any party for any direct or indirect damages resulting from the use of the Customer Support section of the Intershop Corporate Web site, including, without limitation, any lost profits, business interruption, loss of programs or other data on your information handling system.