Hot Topics
- Home
- /
- Cartopret Overview
- /
- Module View
Figure 1 – provides module view of Cartopret showing partner on-boarding & maintenance cycle that are supported through it’s different modules. The functions provided by each module are summarized in this diagram.
Module View
Introduction
Cartopret is a browser based B2B solution that simplifies the process of on-boarding and maintaining trading partners. It offers a comprehensive set of tools for the analyst to create, validate, test and deploy mapping relationships across multiple trading partners. Cartopret seamlessly connects with trading partners and fulfillment systems through a variety of communication protocols and adapters. It provides extensive search and reporting capabilities for support teams and business users in their familiar terminologies. Below is a description of the modules in Cartopret.
Partner
- Partner maintenance: Trading entity details are maintained in this module including DUNS number, status and description. A partner can be classified for test or production.
- Ids setup: Cartopret supports multiple ids for partner to cater to sites/divisions that may be present within a trading entity. Ids for partner units are setup as external ids. Internal identification such as vendor or customer number in fulfillment systems are setup as internal ids.
- Communications setup:Communication protocols supported include Web Service, HTTPS and FTP. Credentials for communication protocol are also maintained as part of partner setup. For web service, synchronous and asynchronous modes of communication are allowed.
- Address maintenance: Physical address, phone numbers and email addresses of different partner entities can be maintained under partner module. Technical and other contact information are also maintained. The technical support contact person, who has to receive error notification from the system, can be marked at partner level.
Interaction
- Interaction maintenance: Interaction defines relationship between partner, business process and the mapping present in the system. If there are multiple fulfillment systems that cater to different business processes for the same partner, it can be selected with just a drop down in Cartopret.
- Cross reference setup: The relation between ids used by partner and the ones present in fulfillment system is established part of this setup. For the external id used for communication, corresponding internal id is chosen to establish this linkage.
Do you wish B2B integration were simple?
The process of integrating B2B partners relies heavily on technology, thus limiting business analyst's ability to work alone. Cartopret helps by masking the technical complexity behind B2B integration.
Document Definition
- Import schema: Cartopret supports multiple ways of defining a document definition. A new document definition can be created from a schema from an industry standard organization or a business partner. Constraints imposed are directly translated as properties for each element within document definition.
- Customize from standard: New document definition can be created based on an existing standard when partner has customized the standard. Properties of the new document definition can be copied from an existing document definition instead of manually updating them.
- Doc Def maintenance: Hierarchical view of the document along with element names and properties can be viewed. Available properties of element include mandatory/optional, active/inactive, attribute, length, repeat count and data type.
- Maintain References: Cartopret provides an option to store actual values from message exchanges for pre-defined elements so that they can be searched upon independently. This feature adds value to business user, who is familiar with the business terminology rather than the xml standards.
Faster onboarding of B2B partners
It takes longer to onboard partners because critical tasks are executed manually and outside the B2B solution. Cartopret automates these tasks ensuring quick partner onboarding.
Mapping
- Map maintenance: Analyzing and implementing mapping relationships are
integrated and simplified in Cartopret. Instead of working on the entire source
and destination document, it lets user to select a subset of elements to WorkSpace,
which are required to implement mapping relationships. Once a set of mapping rules
are established, they can be saved and moved on to the next set thus making the
mapping process modular.
Mapping relationship can be a mapping rule or a validation rule. Mapping rules are assigned to destination elements, whereas validation rules are assigned to source elements. Conditions that have to be satisfied for business process can be implemented as validation rules. On failure of a validation rule, user can decide to generate a warning and continue with the map or to terminate the map. - Validate exceptions: Mapping rules are validated for exceptions. This automatically analyzes the gap between source and destination elements and creates an exception in case of any discrepancy. These exceptions are stored in exceptions tab for quality control. An exception once created can either be fixed by changing source/destination properties or ignored. Exception list can also be downloaded to an Excel.
- Deploy map: Map, when it is free of exceptions (either ignored or resolved) can be deployed, which then can be used for runtime translations.
Simplifying e-commerce in business
Cartopret simplifies B2B integration by masking technical complexity and through increased automation. This helps to rapidly and reliably enable supply chain partners for electronic commerce.
Testing
- Test mapping relationships: With Cartopret, each mapping relationships can be independently tested. This can be done even before assigning the map to an interaction. Individual mapping or validation rules can be tested by providing the relevant source data. Required test criteria can be evaluated by changing input values to the mapping relationships.
- Test complete map: This allows the complete map to be tested as a single entity. Source values can be imported from a file and map evaluated to obtain results. This iteration can be repeated by just changing input values on the screen and re-evaluating the map. The result can also be exported as a destination file.
Transaction
- Search transaction: Cartopret allows runtime transactions that to be searched based on multiple parameters. This search can be based on status, ids, document number etc. Each transaction is assigned a unique id in the system called message id, which will be referenced in error notifications.
- View transaction: Complete source and destination document along with other transaction details can be viewed for a transaction. Any translation errors also will be listed along with detailed error message.
- Search by reference: Transactions can be searched based on business names of elements (provided earlier during document definition setup). Actual values in real time transactions will be listed along with the transaction id in search results.
Lower risk of B2B transactions
B2B transactions are at risk because setup complexities make it difficult to thoroughly test all scenarios. Cartopret reduces the risk by providing an integrated test environment.
Recent Links :
Faster onboarding of B2B partners
It takes longer to onboard partners because critical tasks are executed manually and outside the B2B solution. Cartopret automates these tasks ensuring quick partner onboarding.
Do you wish B2B integration were simple?
The process of integrating B2B partners relies heavily on technology, thus limiting business analyst's ability to work alone. Cartopret helps by masking the technical complexity behind B2B integration.
