|
| |
| |
| |
|
|
|
| Free Download SAP Business Warehouse(BW) Books And |
| BW Planning Sequences,BW Standard Key Date in Planning Functions,BW Currency Translation,BW Distribution by Reference Data,SAP BW Distribution by Key,SAP BW Revaluation,SAP BW Repost by Characteristic Relationship,BW Repost,HOW to Ignoring Initial Zeros in SAP BW # BW Logging Statistical Key Figures # BW Trend Dampening |
| Language: |
| RSS Feeds for this Blog |
|
Statistics |
| Unique Visitors: 29 |
| Total Unique Visitors: 31844 |
| Visitors Out: 348 |
| Total Visitors Out: 348 |
|
|
|
| |
|
|
| |
|
| SAP BI Creating InfoSets |
| 2008-04-08 09:53:49 |
Prerequisites Make sure that the objects for which you want to define the InfoSet are active. Create any required InfoObjects that do not exist already and activate them. Instead of creating a new InfoSet, you can transfer one of the InfoSets that are delivered with SAP Business Content. Procedure ... 1. You are in the InfoProvider tree of the Modeling function area in the Data Warehousing Workbench. Choose the Create InfoSet function from the context menu of the InfoArea in which you want to create an InfoSet. The Create InfoSet dialog box appears. 2. Enter the following descriptions for the new InfoSet: ¡ Technical name ¡ Long name ¡ Short name (optional) 3. In the Start with InfoProvider section, you determine whi...
|
| |
|
| Editing InfoSets |
| 2008-04-08 09:53:17 |
Prerequisites Before you can get to the screen where you edit InfoSets, the following prerequisites have to be met: ● You have created a new InfoSet. ● You have selected the Change function from the context menu of an InfoSet entry in the InfoProvider tree of the Modeling function area in the Data Warehousing Workbench. ● You have called the InfoSet Builder transaction, and selected the Change function. For more information see Additional Functions in the InfoSet Builder. Procedure ... 1. The Change InfoSet screen is displayed. Choose a layout for the InfoProvider tree: InfoAreas Related InfoProvider All DataStore Objects All InfoObjects All InfoCubes The default value is Related InfoProviders. Changed settings are personalize...
|
| |
|
| Special Features of InfoCubes in SAP BI InfoSets |
| 2008-04-08 09:52:31 |
Use InfoCubes are handled logically in InfoSets like DataStore objects. This is also true for time dependencies. Features Request Status In an InfoCube, the system can read data with different request statuses. In the table view of the InfoCube, you make this setting in the context menu of the rows. When you use InfoCubes in InfoSets, you can set the request up to which you want to rollup data in the aggregate (rollup), and the request up to which the data is qualitatively correct (qualok). You make these settings in InfoCube administration. The default for qualok is all green requests, where no yellow or red requests exist before them. For example, requests 1-23 are rolled up into aggregates. Requests 1-27 are qualitatively correct. In the context of the InfoCube in the InfoSet,...
|
| |
|
| Additional Functions in the SAP BI InfoSet Builder |
| 2008-04-08 09:52:08 |
You can also use transaction RSISET to call up the InfoSet Builder when you want to edit an InfoSet. Select the InfoSet that you want to edit. Input help is available for this. Additional functions are also available to help you edit and manage your InfoSet. Compare You use this function from the main menu to check if the InfoProviders used in the InfoSet have been changed and the InfoSet needs to be adjusted as a result. For more information, see Comparing InfoSets. Jump to object maintenance You use the InfoObjects, DataStore Objects and Standard InfoCube functions to jump to the maintenance screen for the InfoProviders included in the InfoSet definition. Info functions There are various info functions on the status of the InfoSets: · ...
|
| |
|
| Screen Layout: Changing SAP BI InfoSets |
| 2008-04-08 09:51:44 |
The Change InfoSet screen has the following areas: InfoProvider Tree On the left-hand side of the screen, all of the InfoProviders that you are able to use in the InfoSet definition are displayed. The options in the following table control how the InfoProvider tree is displayed: InfoProvider Tree What You Need to Know InfoArea This tree contains all the DataStore objects, InfoCubes and InfoObjects that are characteristics (with master data), that are available in the BI system. These are arranged according to InfoArea. Choose the Expand Nodes option from the context menu of an InfoArea to display all of the objects that belong to this particular InfoArea, in a hierarchy . If you do not want to display the lower levels, choose the Colla...
|
| |
|
| SAP BI Matching InfoSets |
| 2008-04-08 09:51:24 |
Use If changes have been made to InfoProviders that are used in InfoSets, you must compare the InfoSet with the modified InfoProviders and make any changes necessary to make the two match again. When you call the InfoSet Builder, the system checks whether the InfoProviders that are used have been changed at all. At this point, you have the option of comparing and adjusting the InfoSets as required. This needs to be done, because otherwise there is a risk that the data will be inconsistent. Features The match (compare and adjust) function for InfoSets checks the following: In the case of DataStore objects and master data-bearing characteristics · Whether attributes/data fields have been added or removed. In the case of Da...
|
| |
|
| SAP BI Infoset Join Control |
| 2008-04-08 09:51:07 |
Definition An area of the screen belonging to the InfoSet Builder. The InfoProviders that are included in the join are displayed in the join control. Use You define join conditions in the join control. There must be valid join conditions before the system is able to activate the InfoSet. For more information, see Defining Join Conditions. The first time you call the InfoSet Builder you can choose between two display modes: network (DataFlowControl) or tree (TreeControl). While the network display is clearer, the tree display can be read by the ScreenReader and is more suitable for visually-impaired users. You can change this setting at any time by choosing Settings ® Display. Changes take effect the next time you call the InfoSet Builder. To edit two InfoProviders from one InfoS...
|
| |
|
| SAP BI Infoset Left Outer Join |
| 2008-04-08 09:50:42 |
Use When defining InfoSets, the objects are usually linked using inner join operators. However, you can also use left outer joins. Left outer joins are not possible for InfoCubes. This would have an adverse affect on performance. Inner join and left outer join are only different where one of the involved tables does not contain any suitable record that meets the join conditions. With an inner join (table1 inner join table2), no record is included in the results set in this case. However, this means that the corresponding record from table 1 is not considered in the results set. In this case, with a left outer join (table1 left outer join table2), exactly one record is included in the results set. In this record, the fields from table1 contain...
|
| |
|
| Examples of Condition Conversion |
| 2008-04-08 09:50:18 |
The following examples show how the Left Outer: Include Filter Value in On-Condition indicator affects the query results. Characteristic ZPRODUCT (T00001), which has master data, contains two data records. #Field (ZPRODUCT) A B DataStore object ZSD_01 (T00002) contains three data records: #Field (ZPRODUCT) #Date (0DATE) ABC Indicator (ABCKEY) A 27.09.2003 X A 01.04.2003 X C 17.05.2003 X In the InfoSet, the two InfoProviders are joined: ZPRODUCT- ZPRODUCT with ZSD_01- ZPRODUCT Note the following cases: Case 1 The objects are joined using an inner join. All the fields are output in the query and a restriction is applied to the date (01.04.2003). If all the objects in the InfoSet are joined using an inner join, this indicator does not effect the S...
|
| |
|
| Editing SAP BI InfoProviders in the Join Control |
| 2008-04-08 09:49:54 |
Use In order to define join conditions between two InfoProviders, you can bring up a new display screen separately and edit there. To get an overview using the InfoProviders contained in the InfoSet, we recommend using the join control for the Change InfoSet screen. For this display a zoom factor of 50%, for example, would be suitable. To edit individual InfoProviders within the InfoSet, we recommend using the separate display of two InfoProviders in the join control for the Editing Selected Objects screen. For this display a zoom factor of 120%, for example, would be suitable. Prerequisites You have transferred the InfoProviders you want from the Change InfoSet screen into the join control. For more information see Editing InfoSets. Procedure ... You are in the Change InfoS...
|
| |
|
| SAP BI Temporal Join |
| 2008-04-08 09:49:38 |
Use You use a temporal join to map a period of time. Other InfoProviders in reporting handle time-dependent master data in such a way that the record valid for a pre-defined unique key date is used each time. Whereas InfoSets are more flexible. They can be used to map periods of time, as in the following case: A DataStore object contains a posting date and a time-dependent characteristic, as well as a key figure. You now want the record for the time-dependent characteristic to be determined according to the posting date, which is different in each record of the DataStore object. InfoSets enable this using temporal operands. Features A temporal join is a join that contains at least one time-dependent characteristic or a pseudo time-dependent Info...
|
| |
|
| Most Recent Reporting for SAP BI InfoObjects |
| 2008-04-08 09:49:11 |
Use This function allows you to report on the master data last loaded into the system, even when they haven’t been activated yet. Functions You can find this function in the InfoSet Builder via the main menu under Goto ® Global Properties ® Most recent Reporting for InfoObjects. If you set this indicator, a most recent reporting is carried out for all master-data bearing characteristics. As a result, the newest records are displayed in the query, even when these have yet to be activated, that is, are still in the M version. See Versioning Master Data. Example You have defined an InfoSet via the characteristic 0COSTCENTER. You are loading master data for the 0COSTCENTER characteristic. After activation, the P table looks like this: Later, you load new records. These are firstl...
|
| |
|
| SAP BI Local Aggregation |
| 2008-04-08 09:48:42 |
Use In the global properties for an InfoSet, you can specify whether a local aggregation it to be used. This setting is used to control how the key figures are grouped. ● If the indicator is set, the key figures are grouped before the join, for all tables involved. ● If the indicator is not set, grouping does not take place until after the table contents are joined. This is the default setting. This setting affects the query results. Example A DataStore object, 'ZZSALES', contains the following data records: #CUSTOMER #MATERIAL #COUNTRY QUANTITY PRICE MILLER 10001 US 5 500 USD MILLER 10001 DE 7 700 USD MILLER 10002 US 3 150 USD MILLER 10002 DE 2 100 USD Another DataStore object, 'ZZMATERIAL', contains the following data...
|
| |
|
| Interpreting Queries Using SAP BI InfoSets |
| 2008-04-08 09:48:17 |
The following explanations and examples are intended to help you understand how queries that use InfoSets work, and to be able to interpret the results correctly. Technical Issues That Affect the Result of the Query The results set of a join is made up of fields from all of the tables involved. One row of this result set contains a valid combination of rows from each of the tables involved. The join condition and the filter for the query that you specify determine which combinations are valid. You can set join conditions between fields from the key part of the tables and between fields from the data part of the tables. For two InfoObjects, for example, you can define an equal join condition between two attributes. The filter for the query determines which values are allowed for indivi...
|
| |
|
| SAP BI Classic InfoSet |
| 2008-04-08 09:47:56 |
Definition A classic InfoSet provides a view of a dataset that you report on. You use the InfoSet query for this purpose. The classic InfoSet determines which tables, or fields within a table, an InfoSet query references. Use As of Release BW 2.0B, InfoSets are used in the Business Information Warehouse for InfoObjects (master data), DataStore objects, and joins for these objects. These InfoSets are not BI Repository objects but SAP Web Application Server objects. The InfoSet query can be used to carry out tabular (flat) reporting on these InfoSets. As of Release BW 3.0, these InfoSets are called classic InfoSets. Integration As of Release BW 3.0A, you can use transformation program RSQ_TRANSFORM_CLASSIC_INFOSETS to avoid having to fully implemen...
|
| |
|
| Setting-up a Role for the SAP BI InfoSet Query |
| 2008-04-08 09:47:38 |
Use To be able to create an InfoSet Query, the system administrator must set up a role for the work with the InfoSet Query. Procedure ... 1. A role has to be assigned specifically to a single SAP Query user group. This is because the InfoSet Query is derived from the SAP Query. a. Call up the Role Maintenance (RSQ10). You get to a table containing the roles that are relevant for working with the InfoSet Query. b. Choose the role you want, and use the Assign User Group function (second column in the table) to assign a user group to the role, or to remove an existing assignment. When you are assigning user groups, a dialog box appears asking you if you want to create a new user group, or use an existing one. Use the input help to choose from the available us...
|
| |
|
| SAP BI Processing Classic InfoSets and Assigning Roles |
| 2008-04-08 09:47:23 |
Use Before you are able to work with the classic InfoSet query, classic InfoSets must already be available that are assigned to particular roles. Procedure There are various ways of getting to the classic InfoSet maintenance screen: · Call transaction RSQ02 InfoSet: Initial Screen. · Call from the context menu of DataStore objects or InfoObjects in the Modeling view of the Data Warehousing Workbench The following deals primarily with BI-specific enhancements. You can find extensive information about the available functions of SAP Application Server InfoSets in the SAP documentation on SAP Query. This information also covers BI classic InfoSets. Defining Classic InfoSets ... 1. In the Data Warehousing Workbench – M...
|
| |
|
| SAP BI InfoSet Query |
| 2008-04-08 09:47:04 |
The InfoSet Query is a tool of the SAP Application Server that can be used in the BI System for tabular (flat) reporting. Classic InfoSets provide the view for this data. Use The InfoSet Query versus the BEx Query The BEx Query is intended for reporting with InfoCubes. In this process, functions such as the following are supported: Reporting with all InfoProviders, using variables, navigation, displaying attributes and hierarchies, characteristic drilldown, currency translations, report-report interface (R-RI), and authorization checks. These functions are also available for reporting using DataStore objects. However, there is a restriction in that you cannot report on more than one DataStore object at a time. The tool designed for this is the InfoSet Query. The InfoSet Query is desig...
|
| |
|
| Creating sap bi InfoSet Queries |
| 2008-04-08 09:46:45 |
Use The InfoSet Query is designed for reporting on data stored in flat tables. It is particularly useful for reporting on joins for master data and joins for DataStore objects. Prerequisites You must take the following steps before you can create Infoset queries: · Set up Roles for the InfoSet Query · Process Classic InfoSets and Assign Roles Procedure Define the InfoSet Query ... 1. Call the Query Builder. There are various ways of doing this: · To call the Query Builder from the corresponding role menu or from the BEx Browser, double-click on InfoSet Query in the menu that is created when you set up a role. · Developers and testers of Classic InfoSets are able to call up the Query Builder directly from the Classic InfoSet overvi...
|
| |
|
| SAP BI MultiProviders |
| 2008-04-08 09:46:16 |
Definition A MultiProvider is a type of InfoProvider that combines data from a number of InfoProviders and makes it available for analysis purposes. The MultiProvider itself does not contain any data. Its data comes entirely from the InfoProviders on which it is based. These InfoProviders are connected to one another by a union operation. Use A MultiProvider allows you to analyze data based on several InfoProviders. See the following examples: Example: List of Slow-Moving Items Example: Plan-Actual Data Example: Sales Scenario Structure A MultiProvider can consist of different combinations of the following InfoProviders: InfoCube, DataStore object, InfoObject, InfoSet, VirtualProvider, and aggregation level. A union operation is used to combine the data from these objects...
|
| |
|
| Creating SAP BI MultiProviders |
| 2008-04-08 09:46:00 |
Prerequisites There is an active version of each InfoObject that you want to transfer to the MultiProvider. Create any InfoObjects that you require that do not already exist and activate them. Instead of creating a new MultiProvider, you can install a MultiProvider from SAP Business Content. Procedure 1. Create an InfoArea to which you want to assign the new MultiProvider. Choose Modeling ® InfoProvider. 2. In the context menu of the InfoArea, choose Create MultiProvider. 3. Enter a technical name and a description. 4. Choose Create. 5. Select the InfoProvider that you want to form the MultiProvider. Choose Continue. The MultiProvider screen appears. 6. Use drag and drop to transfer the required InfoObje...
|
| |
|
| Consistency Check for Compounding |
| 2008-04-08 09:45:44 |
With regard to compounding, characteristics and navigation attributes have to be identified consistently within a MultiProvider. Otherwise the query results may be inconsistent. Data records may appear in the MultiProvider that do not physically exist in any of the InfoProviders in the MultiProvider. The system checks for consistency. If a MultiProvider is not consistently modeled, it cannot be activated. The system produces an error message. However, you can change this to a warning. This allows you to activate the MultiProvider anyway. Only do this if you are certain that it will not result in inconsistent values. If you have upgraded from SAP BW 3.x to SAP NetWeaver 2004s, MultiProviders defined in SAP BW 3.x may be seen as being incorrect and can n...
|
| |
|
| Dividing a SAP BI MultiProvider Query into Sub-Queries |
| 2008-04-08 09:45:23 |
Use A query based on a MultiProvider is divided internally into sub-queries. A sub-query is generated for each InfoProvider belonging to the MultiProvider. Features The division of a MultiProvider query into sub-queries can be very complex. If you have defined a query for a MultiProvider and want to see how the query has been sub-divided, call transaction RSRT. This can be a useful step if your query does not behave as expected. To see how the query is divided, proceed as follows: Use RSRT to execute the query with the Execute + Debug option. Choose the Explain MultiProvider option. The upper area of the screen, in which the query result is displayed, contains messages with information about how the query has been divided. You may see the following messages: ● DBMAN 133: There ...
|
| |
|
| SAP BI MultiProvider Example: Plan-Actual Data |
| 2008-04-08 09:44:28 |
You have one InfoProvider with the actual data for a logically related business area and one equivalent InfoProvider with the plan data. To compare the actual data with the planned data in one query, you combine the two InfoProviders into one MultiProvider. This is a homogeneous data model. Homogeneous MultiProviders consist of InfoProviders that are technically the same, for example, InfoCubes with exactly the same characteristics and similar key figures. In this case, the InfoCube with the plan data contains key figure Planned Costs and the InfoCube with the actual data contains key figure Actual Costs. Homogeneous MultiProviders represent one way in which you can achieve partitioning within modeling.Example: SAP BI M...
|
| |
|
| Example: SAP BI Multiproviders Sales Scenario |
| 2008-04-08 09:43:53 |
You want to model a sales scenario that is made up of the sub-processes order, delivery and payment. Each of these sub-processes has its own (private) InfoObjects (delivery location and invoice number, for example) as well as a number of cross-process objects (such as customer or order number). It makes sense here to model each sub-process in its own InfoProvider and then combine these InfoProviders into a MultiProvider. It is possible to: ● Model all sub-scenarios in one InfoProvider, or ● Create an InfoProvider for each sub-scenario, and then combine these InfoProviders into a single MultiProvider. The second option usually simplifies the modeling process and can improve system performance when loading an...
|
| |
|
| ALPHA Conversion Routine BI InfoObject |
| 2008-04-07 12:58:47 |
Use The ALPHA conversion is used in the BI system for each presetting for character characteristics. The ALPHA conversion routine is registered automatically when a characteristic is created. If you do not want to use this routine, you have to remove it manually. The ALPHA conversion routine is used, for example, with account numbers or document numbers. Features When converting from an external into an internal format this checks whether the entry in the INPUT field is wholly numerical, whether it consists of digits only, possibly with blank spaces before and/or after. If yes, the sequence of digits is copied to the OUTPUT field, right-aligned, and the space on the left is filled with zeros (‘0’). Otherwise the sequence of digits is copied to ...
|
| |
|
| BUCAT Conversion Routine BI InfoObject |
| 2008-04-07 12:58:27 |
Use The BUCAT conversion routine converts the internal presentation of the budget type (0BUD_CAT) into the external presentation (0BUD_CAT_EX), using the active entries in the master data table for the budget type InfoObject (0BUD_CAT). Example Conversion from the external into the internal format: '1' ® 'IM000003'WBSEL Conversion Routine BI InfoObjectSDATE Conversion Routine BI InfoObjectConversion Routine RSDAT BI InfoObjectIDATE Conversion Routine BI InfoObjectREQID Conversion Routine BI InfoObjectREQID Conversion Routine BI InfoObjectPROJ Conversion Routine BI InfoObjectPOSID Conversion Routine BI InfoObjectPERI7 Conversion Routine BI InfoObjectPERI6 Conversion RoutinePERI5 Conversion Routine BI InfoObjectNUMCV Conversion Routine BI InfoObjec...
|
| |
|
| EAN11 Conversion Routine BI InfoObject |
| 2008-04-07 12:58:11 |
Use The EAN11 conversion routine is used for European Article Numbers (EAN) and the American Universal Product Code (UPC). Features It converts the external presentation, according to settings in transaction W4ES (in the ERP system), into the internal SAP presentation. In the SAP system, left-hand zeros are not saved as, according to EAN standards, these are not required. For example, the EAN ‘123’ is the same as the EAN ‘00123’. As such, the left-hand zeros are dispensed with. UPC-E code short forms are converted into the long form. The EAN11 conversion routine formats the internal presentation of each EAN type, according to settings in transaction W4ES, for output. This ensures that the internal presentation does have left-hand zeros, ...
|
| |
|
| GJAHR Conversion Routine BI InfoObject |
| 2008-04-07 12:57:56 |
Use Conversion routine GJAHR is used when entering the business year in order to allow an abbreviated, two-digit entry. A business year has four digits in the internal format. Functions When converting from an external into an internal format this checks whether the entry in the INPUT field is wholly numerical, whether it consists of digits only, possibly with blank spaces before and/or after. ... 1. If a two-digit sequence of numbers is entered then these are put in the third and fourth spaces of the OUTPUT field. The left-hand spaces are filled with 19 or 20 according to the following rule: ¡ Two-digit sequence ¡ Two-digit sequence >= 50. Fill from left with 19. 2. A sequence that does not have two...
|
| |
|
| ISOLA Conversion Routine BI InfoObject |
| 2008-04-07 12:57:18 |
Use Conversion routine ISOLA converts the two-digit ISO language abbreviation INPUT into its SAP-internal OUTPUT presentation. Functions These are assigned using the LAISO and SPRAS fields in table T002. An INPUT that cannot be converted (because it is not defined as T002-LAISO) produces an error message and triggers the UNKNOWN_LANGUAGE exception. Because they are compatible, single-digit entries are supported in that they are transferred to OUTPUT unchanged. They are not checked against table T002. The difference between upper and lower case letters is irrelevant with two-digit entries however with single-digit entries, upper and lower case letters stand for different languages.WBSEL Conversion Routine BI InfoObjectSDATE Conversion Routine B...
|
| |
|
| MATN1 Conversion Routine BI InfoObject |
| 2008-04-07 12:56:08 |
Use This conversion routine changes internal material numbers, stored in the system, into the external material numbers displayed in the interface and vice versa, according to settings in transaction OMSL. With regard to the specific details of the conversion, read the help for the appropriate input field of the transaction.WBSEL Conversion Routine BI InfoObjectSDATE Conversion Routine BI InfoObjectConversion Routine RSDAT BI InfoObjectIDATE Conversion Routine BI InfoObjectREQID Conversion Routine BI InfoObjectREQID Conversion Routine BI InfoObjectPROJ Conversion Routine BI InfoObjectPOSID Conversion Routine BI InfoObjectPERI7 Conversion Routine BI InfoObjectPERI6 Conversion RoutinePERI5 Conversion Routine BI InfoObjectNUMCV Conversion Routine BI In...
|
| |
|
| NUMCV Conversion Routine BI InfoObject |
| 2008-04-07 12:55:55 |
Functions When converting from an external into an internal format this checks whether the entry in the INPUT field is wholly numerical, whether it consists of digits only, possibly with blank spaces before and/or after. If yes, the sequence of digits is copied to the OUTPUT field, right-aligned, and the space on the left is filled with zeros (‘0’). Otherwise the blank characters are removed from the sequence of digits, the result is transferred, left-aligned, into the output field, and this is then filled from the right with blank characters. Converting from the internal format into the external format (conversion routine CONVERSION_EXIT_NUMCV_OUTPUT) does not produce any changes. The output field is set the same as the input field. Example...
|
| |
|
| PERI5 Conversion Routine BI InfoObject |
| 2008-04-07 12:55:45 |
Use The PERI5 conversion serves to convert a five-figure calendar quarter in an external format (Q.YYYY, for example) into the internal format (YYYYQ). Y stands for year (here four digits) and Q for quarter (single digit: 1,2,3, or 4). The separator (‘.’ or ‘/’) has to correspond to the date format in the user settings. Features Permitted entries for the date format DD.MM.YYYY are QYY (two digits for year without separator), Q.YY (two digits for year with separator), QYYYY (four digits for year without separator), and Q.YYYY (four digits for year with separator). Permitted entries for the date format YYYY/MM/DD would be YYQ, YY/Q, YYYYQ, YYYY/Q. Example Examples where the date format in the user settings is DD.MM.YYYY. A conversion from th...
|
| |
|
| PERI6 Conversion Routine |
| 2008-04-07 12:55:31 |
Use Conversion routine PERI6 is used with six-digit entries for (fiscal year) periods. Features The internal format for six-digit periods is YYYYPP (200206, for example, for period 06 of fiscal year 2002). When the external format is converted to the internal format, this checks whether the entries in the INPUT parameter with external date format (separators, order) comply with user settings. The separator (‘.’ or ‘/’) has to correspond to the date format in the user settings. Different abbreviated entries are possible and these are converted correctly into the internal format. Example For the external date format DD.MM.YYYY in the user settings, the following conversion takes place from external to internal formats: ... 1. ...
|
| |
|
| PERI7 Conversion Routine BI InfoObject |
| 2008-04-07 12:55:14 |
UseConversion routine PERI7 is used with seven-digit entries for (fiscal year) periods.FeaturesThe internal format for seven-digit periods is YYYYPPP (2002006, for example, for period 006 of fiscal year 2002). When the external format is converted to the internal format, this checks whether the entries in the INPUT parameter with external date format (separators, order) comply with user settings. The separator (‘.’ or ‘/’) has to correspond to the date format in the user settings.Different abbreviated entries are possible and these are converted correctly into the internal format.ExampleFor the external date format DD.MM.YYYY in the user settings, the following conversion takes place from external to internal formats:... 1. '012.1999' ...
|
| |
|
| POSID Conversion Routine BI InfoObject |
| 2008-04-07 12:54:59 |
Use The POSID conversion routine converts the external presentation of the program position (0PROG_PO_EX) into the internal presentation (0PROG_POS), using the active master data table entries for the program position InfoObject (0PROG_POS). Example Conversion from the external into the internal format: P-2411 ® P24110000WBSEL Conversion Routine BI InfoObjectSDATE Conversion Routine BI InfoObjectConversion Routine RSDAT BI InfoObjectIDATE Conversion Routine BI InfoObjectREQID Conversion Routine BI InfoObjectREQID Conversion Routine BI InfoObjectPROJ Conversion Routine BI InfoObjectPOSID Conversion Routine BI InfoObjectPERI7 Conversion Routine BI InfoObjectPERI6 Conversion RoutinePERI5 Conversion Routine BI InfoObjectNUMCV Conversion Routine BI ...
|
| |
|
| PROJ Conversion Routine BI InfoObject |
| 2008-04-07 12:54:47 |
Use There are extensive possibilities in the ERP system project system for editing the external presentation of the project and PSP elements (project coding, editing mask). These features are included in the ERP conversion routine. This comprehensive logic cannot be mapped in the BI system. For this reason, the characteristic 0PROJECT_EX exists in the attributes of InfoObject 0PROJECT and the external description is stored there. As the external description is entered on the screen, conversion routine 'CONVERSION_EXIT_PROJ_INPUT' reads the corresponding internal description 0PROJECT and uses this for internal processing. If no master data has been loaded into the BI system (master data generated by uploading transaction data), then the internal descr...
|
| |
|
| REQID Conversion Routine BI InfoObject |
| 2008-04-07 12:54:31 |
Use The REQID conversion routine converts the external presentation of the appropriation request (0APPR_REQU) into the internal presentation (0APPR_RE_ED), using the active entries in the master data table for the appropriation request InfoObject (0APPR_RE_ED). Example Conversion from the external into the internal format: P-2411-2 ® P24110002WBSEL Conversion Routine BI InfoObjectSDATE Conversion Routine BI InfoObjectConversion Routine RSDAT BI InfoObjectIDATE Conversion Routine BI InfoObjectREQID Conversion Routine BI InfoObjectREQID Conversion Routine BI InfoObjectPROJ Conversion Routine BI InfoObjectPOSID Conversion Routine BI InfoObjectPERI7 Conversion Routine BI InfoObjectPERI6 Conversion RoutinePERI5 Conversion Routine BI InfoObjectNUMCV ...
|
| |
|
| IDATE Conversion Routine BI InfoObject |
| 2008-04-07 12:54:02 |
Use This conversion routine assigns the appropriate internal date presentation (YYYYMMDD) to an external date (01JAN1994, for example). Call up the test report RSSCA1T0 to be able to better visualize the functionality of this routine. This test report contains the complete date conversion with external as well as internal presentations. Example Conversion from the external into the internal format: '02JAN1994' ® '19940102'WBSEL Conversion Routine BI InfoObjectSDATE Conversion Routine BI InfoObjectConversion Routine RSDAT BI InfoObjectIDATE Conversion Routine BI InfoObjectREQID Conversion Routine BI InfoObjectREQID Conversion Routine BI InfoObjectPROJ Conversion Routine BI InfoObjectPOSID Conversion Routine BI InfoObjectPERI7 Conversion Ro...
|
| |
|
| Conversion Routine RSDAT BI InfoObject |
| 2008-04-07 12:53:48 |
Use Converts a date in an external format into the internal format. Features First, the system tries to convert the date in accordance with the user settings (System ® User Profile ® Own Data ® Fixed Values ® Date Format). If the system cannot perform the conversion in this way, it automatically tries to identify the format. Valid formats: DD.MM:YYYY MM/DD/YYYY MM-DD-YYYY YYYY.MM.DD YYYY/MM/DD YYYY-MM-DD For automatic recognition, the year has to be in four-digit format. If the date is specified as 14.4.72, this is not unique and can cause errors. Note: If the system can sensibly specify a date from the format in the user settings, this conversion is performed. In this example, if the format in the user settings is DD.MM.YYY...
|
| |
|
| |
 |
