What's New in BackOffice Associates® SolutionsSAP Accelerators by BackOffice Associates® 6.2

This topic contains

New Features

dspCompose™

  • dspCompose™ is a generic governance engine used with SAP Master Data Governance (MDG). It provides industry-specific content and workflows to initiate process governance scenarios for data domains not already handled by SAP MDG, such as Human Capital Management (HCM), Bill of Materials (BOMs), and routings. This strategy results in reduced development cycle time and faster achievement of master data objectives while fully leveraging SAP MDG.

  • dspCompose™ is a workflow-enabled application to govern the entry, review and approval of a proposed mass change. Users are assigned to roles, which are associated with templates. A template aligns with a single BDC or GUI script, an Integrate template, or a custom template, and can be reused for multiple requests. A request drives the workflow process to mass change a single object in SAP.

  • Refer to Requests vs. Templates for more information.

  • Highly customizable, dspCompose™ can be configured to control user access to request data and how a request is processed from request data entry through review and posting to a target system.

  • A change can be based on a database view utilizing a Where clause, an Excel spreadsheet, or manual input by the user. BDC and GUI scripts can be used to update data in a target ERP system such as SAP. Messages are returned from the target system to show which objects were successfully updated.

  • dspCompose™ supports mass change data to be posted to SAP via Integrate, a BackOffice component used as the posting mechanism and script repository. Integrate contains all the commands for every BDC and GUI script used to load data into SAP. Each script represents a mass update process. Refer to Integrate for more information.

    Integrate

    Custom fields can be added to BDC Script templates. Use custom fields when conditional screen execution is required and the data for existing template fields is not adequate. Refer to Add Custom Fields to a BDC Script Template  for more information.

    Transform

    ReportsOnly WebApp group.

    Enhancements

    Integrate

    The Create BAPI Template icon has been added to the Templates page's Vertical View for use with BAPI/RFC template types. When a user clicks this button, Integrate retrieves the metadata for the template prior to validating the template to save processing time.

    Enhancement Requests

    The message type setting can be configured for a Developer assigned to the target or source. When a mapping is reset or submitted for approval on the Field Mappings page in Map, a Developer can choose to receive a notification via email, to receive a popup notification from within the product, or not to receive emails and notifications.

    As a result of requests from the field, the following enhancements were added to the product.  

    • In Console, the following field values have been changed:

    Process Area ID: Each value is a concatenated value that is comprised of the Process Area name and the description (<Process Area name> + ‘-‘ + <description>).

    OBJECT ID: Each value is a concatenated value that is comprised of the object name and the description (<object name> + ‘-‘ + <description>).

    • In Console, an object can be moved between Wave Process Areas and will retain all the history and metrics for the object in the Wave.
    • In Target Design, a System Type without tables cannot be imported. If a System Type without tables is imported, an error displays. A System Type table without fields can be imported. The table is added to Target Design with no fields.
    • In Map, the Cross Reference Load Sequence page was removed.
    • In Map, a Rulebook report is generated automatically for each target. Business Validators use the Rulebook reports during PreLoad validation to compare the mapping rules listed on the Rulebook report to the PreLoad report.
      The Rulebook report:

    Includes all the mapping fields for the source and target

    Includes relevancy criteria for mapping fields

    Does not display GUIDS

    NOTE: GUIDs are available in a view in the database, saved with the naming convention [Target table name] _debugRuleBookSel.

    • In Collect, the BOA RFC using Options package type was removed as an option.
    • In Collect, once a Target is built, a list of tables is published into a group Group that can then be used to publish the same list of Targets / Rules to a new Target. (e.g. dgSAP to dgQR1 to dgSR1 to dgPR1).
    • In Collect, the Fetch process creates groups by schema owner. A group is added for each schema with the naming convention of <source>_<schemaowner>.
    • In Collect, when a table entry uses a CranPort package, it is hyperlinked to the CranPort package in Assemble.
    • In Collect, when deactivating a table, the DTS Package is not removed and the Built check box on the Tables page remains checked.
    • In Collect, when viewing data in the table TEXT_SAP in the dsSAP target, the IDENT field is translated to Identifier and the TDNAME field is translated to Text Name.
    • When a package type is changed to a manual package type (DTS, SSIS, and DataServices) the package name is not changed. The package type must be from the AutoGenerate Package of the same type.
    • In Construct, the Address Server and Duplicates page were removed.
    • In dspMonitor™, when a user adds a report to a group, the METRICS check box on the Group Reports page is enabled by default. dspMonitor™ tracks metrics for the group report on the reports accessed by clicking Dashboard > Metrics in the Navigation pane.
    • In SQL Automation, to view information about the source in Map, including field mappings and the source schema, click Map Source on the Page toolbar on the Automation SQL Target Source page.
    • In Transform, when a target is made inactive, it does not display in Transform.
    • In Transform, on the Horizontal View of the Target Rules and Target Source Rules pages, the DESCRIPTION field length has been increased to 100 characters.
    • In Transform, only rules or views that follow the standard naming convention display in list boxes on the Target Rules and Target Source Rules pages. Refer to Naming Conventions for more information.
    • In Transform, the default record count for a newly registered report is NULL.
    • In Transform, on the Monitor page’s Horizontal View, GUIDs no longer display for sources or targets.
    • In Transform, if a user saves a target export with an export type of Local File, an Assemble tab-delimited package is created and registered to the export.
    • In dspTrack™, when a user clicks the Next Action button on the Work List for a task whose status is Waiting on Dependency, a message displays indicating the task(s) and dependencies that prevent the selected task from moving to the next status.
    • An object’s priority set in Console cascades down to Target Design. Once the target that belongs to the object is synced with Map, the priority is also available in Map, and displays on the Objects page (Process Area Launch > Objects). The priority is also used in Transform, but can be updated in Transform to change the order the object is processed.

    WARNING: Customizations made to any component of thedelivered BackOffice Solution will be overwritten in the next upgrade. To preserve customizations, make a copy of the customizations prior to applying any upgrade.

    A customization is a change to the underlying source code, which differs from configuration – normal setup of the software, such as setting up workflows and defining parameters via the configuration pages.

    Previous Versions