PRPS-USR06 decimal notation problem

After enhancing the datasource 0WBS_ELEMT_ATTR with the two additional user fields  USR06 (UF value 1 WBS) and USE06 (UF unit value 1 WBS) I encountered some strange behaviour.

This began when I extracted data from the ECC source system and I saw that the notation of the user value (after DSO activation) was different from the value filled in by the end user. SAP note 1646349 summarizes this problem. It states that the USR06 and USR07 fields of the PRPS table are always stored with 3 decimals places.
SAP Knowledge Base Article - 1646349 - Decimal Shift in User Currency Fields
For this problem I have developed some lines of ABAP code. The logic uses the TCURX table to calculate how many places decimal must shift for each user value known in the RESULT_PACKAGE. Use this ABAP code inside a transformation to get the same user value as maintained in ECC.

SAP tables related to transports

In some cases it might be interesting to know which SAP BW objects are attached to a specific transport for e.g. release management. Instead of copy and pasting object values mentioned in the SE10 transaction SAP tables can be used.

All information related to SAP transports is stored in E07* tables. An overview of these tables is shown below. Along with this information and this table overview you have the ability to compose an overview of objects (including their functional description) belonging to specific transport.

E070Change & Transport System: Header of Requests/Tasks
E070AChange & Transport System: Attributes of a Request
E070CCTS: Source/Target Client of Requests/Tasks
E070CREATEChange & Transport System: Creation Date of Request
E070CTVGenerated Table for View E070CTV
E070DEPChange & Transport System: Dependencies of Requests
E070LCTS: Index for Assigning Numbers to Requests/Tasks
E070MCTS: Target Package/Layer for Requests
E070TCHelp Table for E070 for Client-Specific Imports
E070USEUse of Current Requests by Users
E070VGenerated Table for View E070V
E071Change & Transport System: Object Entries of Requests/Tasks
E071CChange & Transport System: Client-Specific Lock Flag
E071ELang. Transport: Positive List for Generic Object Selection
E071KChange & Transport System: Key Entries of Requests/Tasks
E071KCChange & Transport System: Key Entries of Requests/Tasks
E071KFChange & Transport System: Nametab Info. on (CHAR)Key Fields
E071KFINIChange & Transport System: Nametab Info. on (CHAR)Key Fields
E071K_30Change & Transport System: Key Entries of Requests/Tasks
E071K_KEYE071K Key Fields
E071SSystem-Specific Import Status of Objects
E071VGenerated Table for View E071V
E07TChange & Transport System: Short Texts for Requests/Tasks
E07T_OLDE07T Before TRKORR Extension

Thanks to for supplying this helpful overview.

Determine standard values of a production order via SAP ECC tables

Ever heard of norm time per operation? If you did, then you don’t have to read further, for those who didn’t please continue.

Last week a business user asked me if it was possible to calculate the norm time per operation on a production order and to add this Key Performance Indicator to an existing BW report. I actually never heard of this KPI. Nonetheless the formula behind it is pretty easy.

Norm time = Base quantity / Standard value of machine

So with this formula in mind my journey began in the SAP ECC source system. Via transaction CO03 I went to a production order and went to an individual operation. Per operation you are able to consult the standard values and the base quantity. The base quantity is straightforward and can be easily extracted via table AFVV.
Standard values of a operation for a specific production order
Extracting standard values is a little bit more complicated, due to the fact that these are attached to a specific work center via a formula parameter. There are multiple standard values available like labor, setup & machine time. For our norm time KPI we are only interested in the machine time.

SAP tables and relations

Sometimes it’s useful to know how the different tables of SAP are related to each other, especially when developing new functionality in BW or ECC. Christopher Solomon and some other (yet unknown) people have composed a .pdf file where per functional area the entities and their relations are graphically displayed. Refer to the attached file to see the result.


ECC source systems appearing in BI folder

Today a colleague noticed that our ECC systems appeared not under the SAP folder, but under the BI folder. This is strange, since ECC is not a BI system. In order to fix this SAP has publishes (of course) an SAP note. (1087980).
ECC source systems appearing in BI folder
This note describes the following steps in order to fix this issue:

1.Check that an entry with SRCTYPE ‘M’ exists in table RSBASIDOC table of ECC source system.
2.Note the values for SLOGSYS and RLOGSYS. It should be same.
3.Run the function module RSAP_BIW_DISCONNECT in the ECC system. NOTE: Never run that function module in a BI system!
4.Enter the following values: I_BIW_LOGSYS <RLOGSYS> as noted in step 2 I_OLTP_LOGSYS  <SLOGSYS> as noted in step 2 I_FORCE_DELETE <X> DO NOT ENTER ANY VALUE IN THE FIELD  – RFC target sys !!!!!
5.Go to RSA1-> Source systems.
6.Select the ECC source system and select RESTORE in the right click menu.

After step 6 has been performed be sure to reactivate all of your transfer structures. If you do not do this the system will not appear under the SAP folder. After you have done this the ECC system should appear in the SAP folder.
ECC source systems appearing in BI folder