onedevatlasBeta
Browse the atlas
AllABAPCAPUI5BTP
PackagePackagetypeA library you install and call yourself.See every one →What this type is →independently maintainedindependently maintainedoriginPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →

pawelwiejkut/bw_remove_characters

An ABAP class for a BW transformation's end routine that strips the characters an InfoObject cannot accept, checked against transaction RSKC, before they cause an activation error.

A flat-file load into BW can carry characters an InfoObject's data type rejects, which then fails activation partway through a DSO load. Put in a transformation's end routine between the flat-file source and the target DSO, the class checks each value with the SAP function module RSKC_CHAVL_OF_IOBJ_CHECK, going by the characters maintained in transaction RSKC, and removes whatever is not allowed. It also stops a value reaching a data type that cannot hold it, char values passed to date fields being the maintainer's example. It installs through abapGit or by copying the class, and is called with a reference to result_package.

GitHub4 ★
Homepage
abaplint254 lines

Facts

Last pushLicenceMIT

Where it sits

Lives in
ABAP
Provides
Loading a warehouseABAPLoading a warehousecapabilityGetting data into an analytical store and keeping it current — connections to source systems, replication and the other integration tasks, import jobs and their lifecycle, and the monitoring that tells you a load failed before a report does. Distinct from [replication](capability:replication), which is an application reading data that lives elsewhere as if it were local rather than a warehouse being filled.

Who is behind it

Paweł WiejkutPaweł WiejkutPersonMaintains this
In the atlas: maintains 2, contributes to 3@pawelwiejkutmaintainer

Before choosing this

Signals

ActivityQuietNo published releases; repository quiet for 24 months

It publishes no releases, and its repository has been quiet for at least 24 full months. This may be normal for stable software; check whether its current state still fits your use.

What it declares

Every artifact

Type
Package
Origin
Independently maintained

As a package

Where it runs
Inside its host
Distributed through
abapGitCopied into the project

Connections1

README

quoted from pawelwiejkut/bw_remove_characters under MIT, read
pawelwiejkut/bw_remove_characters/README.mdOn GitHub

Remove special characters in BW transformations

Welcome at github BW tool for remove special characters, fell free to contribute and create pull requests.

If you have frequent data load from flat files in your BW, you know that user can provide wrong characters into. To prevent activation error of this data, please use this development in your transformation end routine on the first layer (RSDS->DSO).

Issue scenario

No all special characters defined in BW can be hanlded by infoobjects. Due to that, if user provide unexpected chart, we get an issue in case of data activation in our BW system:

Issue

or other informations like:

  • Value ‘#’ (hex. ‘2300’) of characteristic contains invalid characters
  • Error when assigning SID: Action VAL_SID_CONVERT InfoObject
  • (hex. ‘500072007A0065006C006500770020006E0061002000720061’) of characteristic contains inva

How it works ?

This development check infoobject based on passed reference table. Best idea is to use this in end routine between flatfile source system and target DSO. You can't use this if your target object is field based instead of inffobect based. If any invaild characters occurs, it will be automatically replaced by nothig ( cuted off).

Why better than other solutions ?

This development uses standard SAP function module RSKC_CHAVL_OF_IOBJ_CHECK, which basically checks every character you are trying to pass to particular infoobject and confirms is that character allowed to be used in. Most of avaible implementations check correctness of passed characters based on SAP note 173241:

!"%&''()*+,-./:;<=>?_0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ

This implementation addiotionaly:

  • prevent you against pass unsupported characters into particular data types, like passing char values to date fields,
  • bases on entries that you provided in RSKC transaction

Usage instructions:

  1. Clone code using ABAP Git or just copy class,
  2. Add following code into end routine to your trnasformations between flatfile datasource and DSO:
DATA(lobj_check) = NEW zcl_bw_validate_special(
ir_ref = REF #( result_package ) ).

lobj_check->validate(
  EXPORTING
    it_tab     =  result_package
    it_monitor =  monitor
  IMPORTING
    et_tab     = result_package
    et_monitor =  monitor ).
  1. Use and be happy !
MIT, read

Others providing3

Compare all 4 on the Loading a warehouse page →
Loading a warehouse
  1. ERPLDuckDB extension reading SAP ERP tables, CDS views and BW queries
  2. bw-modeling-mcpMCP server for BW/4HANA modelling objects
  3. pawelwiejkut/bw_trfn_pocketknifeFramework for BW transformation start routines from a table

Details

Sources3
dotabapdiscovered herechecked
github.com/pawelwiejkut/bw_remove_characterstree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
discovered viadotabap
first seen in the atlas
ecosystem and domainabap, data-and-persistence
abaplint
issues under its own abaplint configuration1
lines254
statements118
objects2
files3
analysed, master
abaplint version2.120.84
read fromabaplint.app,
History in the atlas1
  1. First seen.
For your agent
Ref
artifact:pawelwiejkut-bw-remove-characters
JSON
/artifacts/pawelwiejkut-bw-remove-characters.json
MCP
Connecting an agent