Massive traduction of infoobject descriptions.
Hi!!
I hope somebody can help me.
We have to traslate many ( about 300 ) infoobject descriptions ( short and long text) in english.
To do it we have done a custom program to update from a CSV file the records of RSDIOBJT ( the master BW table of text of infoobject ) with the new records with key-linguage "E" ( english ) en version "A".
The program works in part:.......
It updates the RSDIOBJT with the new text in english linguage.
Whe I see, by RSA1 tc, the tree of the infoobject, I see the english name that i have carried by the program.
But if i go in the maintenance ( modify ) mode of the infobject, the upper fields of the infoobject screen ( long and short description ) are blanks.
So that, in reporting i watch only the technical name of the object and not the english description that i carried by the program.....
I wouldn't insert manually the description of 300 infoobjects into english linguage.
Somebody can help me???
Thank in advance!!!
Bye
Fabio
Your program must update also the version "D" and "M" for all infoboject.
Mario
Similar Messages
-
How to change infoobject descriptions in a query after change the infoobjec
Hi all,
Imagine that you have 200 queries in production and need to change some descriptions in 2 infoobjects. eg:
Infooject 1 = "Customer Sales View"
Changed to "Cust.View of New MKT"
Infooject 2 = "Material for sales"
Changed to "Material"
Is there any way to change all queries automatically ? Via Report or Function or Transaction ?
Suggestions ?
Best Regards,
Mauro.Hello Madhukar,
We recently had upgraded to NW2004s and in few queries even when I login with different language for instance Portugese the infoobject descriptions still show up in english and are not changed.
Can you please let me know if I need to update the RSZELTXT table along with other tables. If so can you please forward me the ABAP Code in order to do the same.
Your help would be really appreciated if you can reply promptly as our UAT is pending on this issue.
Let me know.
Thanks
Dharma. -
Infoobject descriptions in Messages of a FOX Formula
Hi Gurus,
consider the following formula
DATA CLIENTE TYPE 0CUSTOMER.
DATA ESPER TYPE 0FISCPER.
FOREACH ESPER,CLIENTE.
IF {#,ESPER} <> 0.
IF CLIENTE <> #.
MESSAGE E001(ZFCMSEM) WITH CLIENTE ESPER.
ENDIF.
ENDIF.
ENDFOR.
when the message appears, You can see the characteristic code and not the description.
Does someone know the way to display description in message?
Thank's in advance.
Regards
Vincenzo CarloneHi,
The whole processing takes place with characteristic values and not texts. Sorry as far as I know no means of getting the text of a characteristic value and displaying it on the message. With 2004s there's an option of calling function modules and then we will be able display text.
hope this was helpful..
thanks -
G/L Description not showing in Query designer for Characteristic values
Hi Friends,
We have developed a report and that we have made two New selections on the object 0GL_account....some GL Account number are grouped in that. While selecting the GL Accounts to new selection, it is showing GL Account number and Description. After that, the selected objects are not showing the Description in the query designer. It is showing GL Account number only for the both Technical name and Description. I Would like to see Description of the GL Accounts in the Query designer. i have plan to delete certain account based on their dercription.
And at the Infoobject description in the Business Explorer tab Display feild it is set as Text and Key. And till yesteday it shown the Description for the Account numbers. The daa loads are also .gone fine.
Can you please guide me in this regards
Thanks & Regards
AnandHi Thanks for your reply.
The accounts which we selected are having Description and it is showing while selection the selected GL Accounts.
And the master data also is in active...When i try to activate the master data Agoin it is saying statement "Master data for characteristic 0GL_ACCOUNTactive"
Any more suggetions..........
Regards,
Anand -
In BW 3.0B, is there an easy way to determine which InfoObjects are used in queries? The Where Used list for individual objects does not include queries. Im really looking for a way of determining which objects are actually used for reporting.
Thanks in advance,
MikeHi Mike,
You can see all queries in table RSRREPDIR , which will have some compressed name of the query in COMPUID field. This field will link it to a cross reference table which lists all the columns and rows of the report (table RSZELTXREF).
The infoobject is stored in this table (RSZELTXREF) in a compressed format, I am not sure where to find the link to the infoobject technical name, but you can find the infoobject description in RSZELTDIR.
This way (RSRREPDIR>RSZELTXREF>RSZELTDIR) you should get close to what you want.
cheers,
Ajay -
Flat File Hierarchy Datasources
We are creating several flat file hierarchy datasources. The datasources will be maintained in an external database.
I am familiar with the creation of flat file datasources for master and transactional data, but don't have good documentation for how the external flat file hierarchy is to be formatted.
We have reviewed the 2004 Netweaver Document "How to Download Hierarchies in BW" and have used the program referenced there, Z_SAP_HIERARCHY_DOWNLOAD, to download our hierarchies to then test the upload.
However, this has not worked.
Does anyone have the record layout that the flat file must be in to upload a simple 2-level hierarchy (for example groupings of 0vendor)?
Thanks, DougI think the URL you mention is http://help.sap.com/saphelp_nw04/helpdata/en/fa/e92637c2cbf357e10000009b38f936/content.htm.
This contains the record layout instructions as follows.
5. Maintaining the hierarchy:
Choose Hierarchy Maintenance, and specify a technical name and a description of the hierarchy.
PSA Transfer Method: You have the option here to set the Remove Leaf Value and Node InfoObjects indicator. As a result, characteristic values are not transferred into the hierarchy fields NODENAME, LEAFFROM and LEAFTO as is normally the case, but in their own transfer structure fields. This option allows you to load characteristic values having a length greater than 32 characters.
Characteristic values with a length > 32 can be loaded into the PSA, but they cannot be updated in characteristics that have a length >32.
The node names for pure text nodes remain restricted to 32 characters in the hierarchy (0HIER_NODE characteristic).
The system automatically generates a table with the following hierarchy format (for sorted hierarchies without removed leaf values and node InfoObjects):
Description
Field Name
Length
Type
Node ID
NODEID
8
NUMC
InfoObject name
INFOOBJECT
30
CHAR
Node name
NODENAME
32
CHAR
Catalog ID
LINK
1
CHAR
Parent node
PARENTID
8
NUMC
First subnode
CHILDID
8
NUMC
Next adjacent node
NEXTID
8
NUMC
Language key
LANGU
1
CHAR
Description - short
TXTSH
20
CHAR
Description - medium
TXTMD
40
CHAR
Description- long
TXTLG
60
CHAR -
How to load hierrarchies using dtp using flat file in bw ineed clear ste
how to load hierrarchies using dtp using flat file in bw ineed clear steps
Hi,
If you want to load InfoObjects in the form of hierarchies, you have to activate the indicator with hierarchies for each of the relevant InfoObjects in the InfoObject maintenance. If necessary, you need to specify whether the whole hierarchy or the hierarchy structure is to be time-dependent, whether the hierarchy can contain intervals, whether additional node attributes are allowed (only when loading using a PSA), and which characteristics are allowed.
1.Defining the source system from which you want to load data:
Choose Source System Tree ® Root (Source System) ® Context menu (Right Mouse Button) ® Create.
For a flat file, choose: File System, Manual Metadata; Data via File Interface.
2.Defining the InfoSource for which you want to load data:
Optional: Choose InfoSource Tree ®Root (InfoSources) ® Context Menu (Right Mouse Button) ® Create Application Component.
Choose InfoSource Tree ® Your Application Component ® Context Menu (Right Mouse Button) ® Create InfoSource ® Direct Update
Choose an InfoObject from the proposal list, and specify a name and a description.
3.Assigning the source system to the InfoSource
Choose InfoSource tree ® Your Application Component ® One of your InfoSources ® Context Menu (Right Mouse Button) ® Assign Source System. You are taken automatically to the transfer structure maintenance.
The system automatically generates DataSources for the three different data types to which you can load data.
Attributes
Texts
Hierarchies (if the InfoObject has access to hierarchies)
The system automatically generates the transfer structure, the transfer rules, and the communication structure (for attributes and texts).
4.Maintaining the transfer structure / transfer rules
Choose the DataSource to be able to upload hierarchies.
Idoc transfer method: The system automatically generates a proposal for the DataSource and the transfer structure. This consists of an entry for the InfoObject, for which hierarchies are loaded. With this transfer method, during loading, the structure is converted to the structure of the PSA, which affects performance.
PSA transfer method: The transfer methods and the communication structure are also generated here.
5.Maintaining the hierarchy:
Choose Hierarchy Maintenance, and specify a technical name and a description of the hierarchy.
PSA Transfer Method: You have the option here to set the Remove Leaf Value and Node InfoObjects indicator. As a result, characteristic values are not transferred into the hierarchy fields NODENAME, LEAFFROM and LEAFTO as is normally the case, but in their own transfer structure fields. This option allows you to load characteristic values having a length greater than 32 characters.
Characteristic values with a length > 32 can be loaded into the PSA, but they cannot be updated in characteristics that have a length >32.
The node names for pure text nodes remain restricted to 32 characters in the hierarchy (0HIER_NODE characteristic).
The system automatically generates a table with the following hierarchy format (for sorted hierarchies without removed leaf values and node InfoObjects):
Description
Field Name
Length
Type
Node ID
NODEID
8
NUMC
InfoObject name
INFOOBJECT
30
CHAR
Node name
NODENAME
32
CHAR
Catalog ID
LINK
1
CHAR
Parent node
PARENTID
8
NUMC
First subnode
CHILDID
8
NUMC
Next adjacent node
NEXTID
8
NUMC
Language key
LANGU
1
CHAR
Description - short
TXTSH
20
CHAR
Description - medium
TXTMD
40
CHAR
Description- long
TXTLG
60
CHAR
The system transfers the settings for the intervals and for time-dependency from the InfoObject maintenance. Depending on which settings you have defined in the InfoObject maintenance, further table fields can be generated from the system.
The valid from and valid to field is filled if you select Total Hierarchy Time-dependent in the InfoObject maintenance. The time-dependent indicator is activated if you select the Hierarchy Nodes Time-dependent option in the InfoObject maintenance.
6.Save your entries.
Depending on which settings you defined in the InfoObject maintenance, additional fields can be generated from the system. Also note the detailed description for Structure of a Flat Hierarchy File for Loading via an IDoc and for Structure of a Flat Hierarchy File for Loading via a PSA.
Also find the below blog for your reference...
/people/prakash.bagali/blog/2006/02/07/hierarchy-upload-from-flat-files
You can load hierarchy using process chain...
Find the below step by step procedure to load hierarchy using process chain...
http://help.sap.com/saphelp_nw70/helpdata/EN/3d/320e3d89195c59e10000000a114084/frameset.htm
Assign points if this helps u...
Regards,
KK.
Edited by: koundinya karanam on Apr 8, 2008 1:08 PM
Edited by: koundinya karanam on Apr 8, 2008 1:09 PM -
Hi gurus
anybody please say a scenario for
1)Exception
2)Condition,
3)Variables,
4)RRI
for FICO based reports... its urgent ..please help me out...
i will assign points
Thanks in advance
pradeepSee below scenarios on which you can implement Exceptions, conditions,........etc on keyfigs.
1. Balance Sheet and P&L: Actual/Actual Comparison
Technical name: 0FIGL_VC1_Q0001
Based on: Virtual InfoCube 0FIGL_VC1
Use
This query is used to display the balance sheet and P&L in two different report periods. The report periods are broken down in the columns, the balance sheet structure/P&L is displayed hierarchically in the report rows.
The balance sheet/P&L is created for exactly one company code. This must be entered using a variable.
Filters
InfoObject Description of the InfoObject (and restriction or calculation formula)
0COMP_CODE Company code, variable 0P_COCD (individual value, required entry)
0VERSION Version, constant value 1
0CURTYPE Currency type, constant value 10 (company code currency)
0VTYPE Version, constant value 10 (actual)
0FISCVARNT Fiscal year variant, variable 0P_FVAEX (SAP exit variable)
User-Defined Characteristics
InfoObject Description
0BUS_AREA Business area
0GL_ACCOUNT General ledger account
Rows
InfoObject Description of the InfoObject (and restriction or calculation formula)
0GLACCEXT Balance sheet/P&L item
Columns
InfoObject Description of the InfoObject (and restriction or calculation formula)
Structure Key figures
0FIGL_VC1_CK001 1. Balance value, calculated key figure for the 0FIGL_VC1:
0FIGL_VC1_CK001 = 0VAL_STOCK + 0VAL_FLOW
Structure Periods:
Report period 1. Selection for characteristic 0FISCPER, variable 0I_FPER
Comparison period 2. Selection for characteristic 0FISCPER, varianble 0FI_FPER2 (= copy of variable 0I_FPER)
Absolute variance 3. Formula:
Report period comparison period
Variance (%) 4. Formula:
Report period % comparison period
2. Bal. Sheet and P&L (Cost-of-Sales Acc.): Actl/Actl Comparison
Technical name: 0FIGL_VC2_Q0001
Based on: virtual InfoCube 0FIGL_VC2
Use
This query is used to display the balance sheet and P&L according to the cost-of-sales accounting method in two different reporting periods. The reporting periods are expanded in the columns, the balance sheet/P&L item (hierarchically) in the reporting rows.
The balance sheet/P&L is created for a single company code that must be entered using a variable.
Filters
InfoObject Description of the InfoObject (and restriction or calculation formula)
0COMP_CODE Company code, variable 0P_COCD (individual value, required entry)
0VERSION Version, constant value 1
OCURTYPE Currency type, constant value 10 (company code currency)
0TYPE Value type, constant value 10 (actual)
0FISCVARNT Fiscal year variant, variable 0P_FVAEX (SAP exit variable)
User-Defined Characteristics
InfoObject Description
0BUS_AREA Business area
0FUNC_AREA Functional area
0GL_ACCOUNT G/L account
Rows
InfoObject Description of the InfoObject (and restriction or calculation formula)
0GLACCEXT Balance sheet/P&L item
Columns
InfoObject Description of the InfoObject (and restriction or calculation formula)
Structure Key figures
Balance sheet value, calculated key figure for InfoCube 0FIGL_VC2:
0FIGL_VC2_CK001 = 0VAL_STOCK + 0VAL_FLOW
Structure Time periods
Report time period Selection for characteristic 0FISCPER, variable 0I_FPER
Comparison period Selection for characteristic 0FISCPER, variable 0I_FPER2 (= copy of variable 0I_FPER)
Variance (absolute) Formula: Report period - Comparison period
Variance (%) Formula: Report period % Comparison period -
Staff Budget / Actual Variance report
Hi,
What is 'Staff Budget / Actual Variance report'.
Is there any Business Content Reports avaliable for this purpose.
Please provide me information on Which Data Target 9Technical Name) i can do this report.
ThanksHi,
This InfoCube contains all costs and quantities on WBS elements (plan and actual using delta extraction, commitment, budget, accruals) that were transferred from the source system(s).
You can also use this InfoCube to access your own fields. For more information, see Customer-Defined Fields.
For background information on the concept of InfoCubes, see InfoCubes in Controlling.
Higher-Level Objects
Queries
The following queries can access this InfoCube:
· 0WBS_C11_Q0001: WBS Element (Detail): Plan/Actual
· 0WBS_C11_Q0002: WBS Elements (List): Budget/Actual/Commitment
· 0WBS_C11_Q0003: WBS Elements (List): Overall Planning/Actual/Commitment
· 0WBS_C11_Q0301: PSM: WBS Element (Detail): Plan/Actual
· 0WBS_C11_Q0002: PSM: WBS Elements (List): Budget/Actual/Commitment
Notes on Query Definition
If you attempt to sum across different valuation views and currency types, your query results will be incorrect. Summing across different values of these characteristics does not provide useful information.
InfoSources
· 0CO_OM_WBS_1: WBS Elements: Costs
· 0CO_OM_WBS_2: WBS Elements: Budget
· 0CO_OM_WBS_3: WBS Elements: Overall Plan
· 0CO_OM_WBS_6: WBS Elements: Actual Costs Using Delta Extraction
Characteristics
InfoObject
Description
0WBS_ELEMT
PSP element
0COSTELMNT
Cost element
0CO_AREA
Controlling area
0CURTYPE
Currency type
0PIOBJSV
Partner object type
0PIOVALUE
Partner object
0METYPE
Key figure category
0VERSION
Version
0VTDETAIL
Details of value type
0VTYPE
Value type for reporting
0DB_CR_IND
Sender/receiver indicator
0VALUATION
Valuation view
0VTSTAT
Statistics indicator for value type
0FM_AREA
FM area
0FUND
Fund
0FUNC_AREA
Functional area
0GRANT_NBR
Grant
0PFUND
Partner fund
0PFUNC_AREA
Partner functional area
0PGRANT_NBR
Partner grant
Navigation Attributes
The following navigation attributes have been activated. This is a sample selection. You are free to activate additional attributes, or deactivate attributes to improve performance.
InfoObject
Description
0WBS_ELEMT__0CO_AREA
Controlling area
0WBS_ELEMT__0PROFIT_CTR
Profit center
Time Characteristics
InfoObject
Description
0FISCPER
Fiscal year/period
0FISCVARNT
Fiscal year variant
0FISCPER3
Posting period
0FISCYEAR
Fiscal year
· The characteristics fiscal year (0FISCYEAR) and posting period (0FISCPER3) are filled by the fiscal year period field (0FISCPER) in the InfoSource.
· The characteristics and the cost element are not filled for overall budgets or overall plan values. The posting period and the cost element characteristic are not filled for annual budgets or annual plan values. This provides values with the format 000.YYYY (where YYYY is the fiscal year), particularly for the 0FISCPER characteristic.
Key Figures
InfoObject
Description
0AMOUNT
Amount
0QUANTITY
Consumption quantity
Restricted Key Figures
The restricted key figures are divided into several groups.
The basic key figures cannot be used without restricting some of the characteristics. For this reason you should use only the supplied restricted key figures in queries you have defined yourself, or analyze the supplied restricted key figures and modify them to suit your requirements.
InfoObject
Restriction
Costs Group
Data for all restricted key figures of the group
Key figure category = 1000 (costs and associated quantities)
Valuation view = 0 (legal valuation)
Version = 0 (current variant)
Key figure = 0AMOUNT (amount)
0WBS_C11_RK0002 Actual costs
Sender/receiver = S (debit posting or receiver debit)
Value type = 10 (actual)
0WBS_C11_RK0001 Planned costs
Sender/receiver = S (debit posting or receiver debit)
Value type = 20 (plan)
0WBS_C11_RK0006 Settled costs
Sender/receiver = H (credit posting or sender debit)
Value type = 10 (actual)
0WBS_C11_RK0003 Commitments
Sender/receiver = S (debit posting or receiver debit)
Value type = 40 (commitment)
0WBS_C11_RK0004 Budget (per fiscal year)
Value type = 50 (budget)
0WBS_C11_RK0005 overall planning (per fiscal year)
Value type = 20 (plan)
Revenues Group
Data for all restricted key figures of the group
Sender/receiver = H (credit posting or sender debit)
Key figure category = 1001 (costs and associated quantities)
Valuation view = 0 (legal valuation)
Version = 0 (current variant)
Key figure = 0QUANTITY (quantity)
0WBS_C11_RK0008 Actual revenue
Value type = 10 (actual)
0WBS_C11_RK0007 Planned revenue
Value type = 20 (plan)
Quantities Group
Data for all restricted key figures of the group
Sender/receiver = S (debit posting or receiver debit)
Key figure category = 1000 (costs and associated quantities)
Valuation view = 0 (legal valuation)
Version = 0 (current variant)
Key figure = 0QUANTITY (quantity)
0WBS_C11_RK0021 Actual consumption quantity
Value type = 10 (actual)
0WBS_C11_RK0022 Plan consumption quantity
Value type = 20 (plan)
WIP Group
Data for all restricted key figures of the group
Sender/receiver = S (debit posting or receiver debit)
Key figure category = 1410 (inventory (WIP))
Valuation view = 0 (legal valuation), version = results analysis version
Value type = 80 (results analysis)
Key figure = 0AMOUNT (amount)
0WBS_C11_RK0011 WIP: Revenue in excess of billings
Detail for value type = 10
0WBS_C11_RK0009 WIP: Work in process
Detail for value type = 1, 2
0WBS_C11_RK0010 WIP: Cannot be activated
Detail for value type = 3
Results Group
Data for all restricted key figures of the group
Sender/receiver = S (debit posting or receiver debit)
Key figure category = 1400 (accrual calculation)
Valuation view = 0 (legal valuation)
Version = accrual version
Value type = 80 (results analysis)
Key figure = 0QUANTITY (quantity)
0WBS_C11_RK0018 Revenue affecting net income
Detail for value type = 12
0WBS_C11_RK0014 Cost of sales
Detail for value type = 3, 4
0WBS_C11_RK0015 Cost of sales (cannot be capitalized)
Detail for value type = 5
0WBS_C11_RK0017 Realized loss
Detail for value type = 11
0WBS_C11_RK0012 Reserves for imminent losses
Detail for value type = 1
0WBS_C11_RK0013 Reserves for imminent losses - inclusion cannot be capitalized
Detail for value type = 2
0WBS_C11_RK0016 Loss
Detail for value type = 10
Reserves Group
Data for all restricted key figures of the group
Sender/receiver = S (debit posting or receiver debit)
Key figure category = 1420 (reserves)
Valuation view = 0 (legal valuation), version = results analysis version
Value type = 80 (results analysis)
Key figure = 0AMOUNT (amount)
0WBS_C11_RK0019 Reserve: unrealized costs
Detail for value type = 1, 2
0WBS_C11_RK0020 Reserve: unrealized costs, not capitalized
Detail for value type = 3
Units
InfoObject
Description
0CURRENCY
Currency key
0UNIT
Unit of measure
Hareesh -
Agewise Stock Report using FIFO out of 0IC_C03
Hello,
I have a requirement where I need to create agewise stock report using FIFO. I have the stock availability from 0ic_c03.
Can any one plese tell me how to achieve the FIFO based agewise stock. I have various age buckets like 0-30 , 30-60, 60-90 etc.
If the total stock is made up of multiple receipts and I also have few issues, how can I get the balance stock based on FIFO using the GR date.
I would appreciate your help.
Regards
VasunHi,
This InfoCube allows you to evaluate stocks from ERP.
A new feature in this InfoCube is the pre-existing stock key figure Valuated Stock Quantity (0VALSTKQTY) and the associated movement key figures Receipt Quantity Valuated Stock (0RECVALSTCK) and Issue Quantity Valuated Stock (0ISSVALSTCK).
This is made possible by including the InfoObject indicator Evaluation Special Stock (0INDSPECSTK) in the InfoSource Material Stocks (as of SAP BW 3.1 Content) (2LIS_03_BX). The InfoSource used up until now, Transfer BW: Stock (2LIS_40_S278), did not recognize this InfoObject.
Note the Remarks on Filling Non-Cumulative InfoCubes.
The following Basis key figures can be restricted in the query definitions to stock categories (0STOCKCAT), such as project stock, and to stock types (0STOCKTYPE), such as quality inspection:
· Quantity of Valuated Stock (0VALSTCKQTY)
· Receipt Quantity Valuated Stock (0RECVALSTCK)
· Issue Quantity Valuated Stock (0ISSVALSTCK)
In this way, for example, you can evaluate the quantity of valuated project stock (Q).
The newly-included Basis key figures are only updated through the InfoSources 2LIS_03_BX and 2LIS_03_BF.
In this way, none of these Basis key figures can be used in queries that are built up on InfoCubes which were inventory-initialized through InfoSource 2LIS_40_S278. Moreover, the queries 0IC_C03_Q0013 to 0IC_C03_Q0016 cannot be used in the combination of InfoSources 2LIS_40_S278 and 2LIS_03_BF.
Note the following procedures when filling the InfoCube 0IC_C03 for the first time with non-cumulative data from ERP:
1. Create non-cumulatives with the program BW: Initialization of Opening Non-Cumulatives in Transfer Structure (RMCBINIT_BW).
2. Initialize the movements/revaluations with the program RMCBNEUB/RMCBNERP.
3. Post in the InfoCube using the update method Creation of Non-Cumulatives from the InfoSource 2LIS_03_BX.
4. Post in the InfoCube using the update method Initialization of the Delta Process from the InfoSources 2LIS_03_BF and 2LIS_03_UM.
Refer to SAP Note 0643687 (Compression of Non-Cumulative InfoCubes) regarding the subsequent steps for compression.
5. Compression of the request from 2LIS_03_BX with update of the marker.
6. Because in this case you are posting movements and revaluations in the InfoCube that occurred before the non-cumulative creation and which lead to this non-cumulative creation, you must execute a compression without updating the marker. For more information, see InfoCubes.
7. Thereafter, you can transfer new movements and revaluations to the BW system as usual (for performance reasons, we recommend that you regularly compress with updates of the marker, see also InfoCube Compression).
Update Logic
When updating the DataSources 2LIS_03_BX, 2LIS_03_UM and 2LIS_03_BX, the System applies the following logic:
Characteristic Value Calculation
In principle, values are updated with Plant, Material, and Stock Category only. Quantities are updated with these characteristics, as well as with Storage Location, Batch Number, and Stock Characteristic (see also SAP Note 589024: Evaluations in BW with the Characteristics Storage Location and Stck Char.).
Key Figure Value Calculation
The source field for quantities is the field CPQUABU, and for values it is the field CPPVLC.
In the update, the InfoSource fields Stock Characteristic and Stock Category control whether "special stock" key figures are updated, such as Quality Stock or Stock in Transit (only relevant for 2LIS_03_BF and 2LIS_03_UM).
The general key figures (for example, Total Stock), however, can also be restricted in queries to Stock Characteristic and Stock Category, and then deliver the same result (key word: account model versus key figure model).
The values for Stock Characteristic and Stock Category are dealt with on the extractor side in the LMCB1F20 include (routine STA_VERAENDERUNG).
The InfoObject 0INDSPECSTK (field KZBWS) also controls whether the sales order stock / project stock is valuated or non-valuated.
The system valuates the transaction key to decide whether the issue movement key figure or receipt movement key figure is updated. For more information, see SAP Note 492828: Determining the transaction key for 2LIS_03_BF + 2LIS_03_UM.
InfoSources
This InfoCube is based on the following InfoSources:
· 2LIS_03_BX
· 2LIS_03_BF
· 2LIS_03_UM
Characteristics
InfoObject
Description
0MATERIAL
Material
0PLANT
Plant
0STOR_LOC
Storage Location
0BATCH
Batch Number
0STOCKTYPE
Stock Type
0STOCKCAT
Stock Categories
0GN_VENDOR
Vendor
Time Characteristics
InfoObject
Description
0CALDAY
Calendar Day
0CALMONTH
Calendar Year/Month
0CALWEEK
Calendar Year/Week
0CALYEAR
Calendar Year
Key Figures
InfoObject
Description
0RECVS_VAL
Value Received - Valuated Stock
0VALSTCKVAL
Value - Valuated Stock
0ISSVS_VAL
Value Issued - Valuated Stock
0ISSBLOSTCK
Issue Quantity - Blocked Stock
0ISSCNSSTCK
Issue Quantity - Consignment Stock
0ISSQMSTCK
Issue Quantity - Inspection Stock
0ISSTRANSST
Issue Quantity - Stock in Transit
0RECBLOSTCK
Receipt Quantity - Blocked Stock
0RECCNSSTCK
Receipt Quantity - Consignment Stock
0RECQMSTCK
Receipt Quantity - Inspection Stock
0RECTRANSST
Receipt Quantity - Stock in Transit
0QMSTOCK
Inspection Stock
0BLOCKEDSTK
Blocked Stock
0CNSSTCKQTY
Quantity - Consignment Stock
0TRANSSTOCK
Stock in Transit
0ISSSCRP
Issue Quantity - Scrap
0ISSVALSCRP
Issue Value - Scrap
0RECTOTSTCK
Receipt Quantity - Total Stock
0ISSTOTSTCK
Issue Quantity - Total Stock
0TOTALSTCK
Quantity - Total Stock
0ISSVALSTCK
Issue Quantity - Valuated Stock
0RECVALSTCK
Receipt Quantity - Valuated Stock
0VALSTCKQTY
Quantity - Valuated Stock
0VENCONCON
Consumption Value - Vendor Consignment Stock
Units
InfoObject
Description
0LOC_CURRCY
Local Currency
0BASE_UOM
Base Un
Regards,
Hareesh -
Report output showing in technical names
Hi,
When I execute a query, input variables and report out put are shown up generally in InfoObject descriptions before. Just suddenly what happened don't know these reports are showing up output in Technical names, Input variables and the report as well. Where do you make this to set as default to display in InfoObjects descriptions input variables and the report as well instead of technical names. Kindly help, I appreciate your answers. Thanks
regards,
reddy
Edited by: chreddeppa on Oct 21, 2011 8:13 PMSometime it happens because of the lanugate setting of the browser.
If the browser is internet explorer, you can go to Tools > Internet Option > General > Language and if you are using English, it should be added there (and I guess as first language).
Try if it solves your issue.
Regards,
Gaurav -
Hello My guru friends
In the activation of the infosources 0FUNCT_LOC and 0GL_ACCOUNT i can´t activate because the system error send my this message 0STARTLEVEL object is not i active version, i went to BCT area to activate it and it don´t exist what dou you know about that.
Whit best regards
AGThi AGT,
there is sap oss note for this, take a look and try the solution proposed. hope this helps.
663945
BW-BCT-FI: Transfer rules for 0GLACCEXT InfoObject Help
SAP Note Number Note Language DEEN Display Versions 1
Print SSCR Download
Text Header Data Release Correction Instructions Support Packages >>
Symptom
BW Release 3.2 Content delivers the 'Balance Sheet and Profit and Loss' scenario.
The most important objects in this context are the virtual InfoCubes
0FIGL_VC1 - General Ledger: Balance Sheet and Profit and Lossand
0FIGL_VC2 - Cost of Sales Ledger:Balance Sheet and Profit and Loss
as well as the following queries, which are based on them
0FIGL_VC1_Q0001 - Balance Sheet and P&L: Actual/Actual Comparison and
0FIGL_VC2_Q0001 Balance Sheet and P&L (Cost-of-Sales Acc.): Actl/Actl Comparison.
When you activate the dependent content for the two queries (using the grouping: In Data Flow Before), the transfer structure and the transfer rules for hierarchies for the 'Balance Sheet/P&L statement item' InfoSource (0GLACCEXT) are missing.
Other terms
0GLACCEXT
Reason and Prerequisites
For technical reasons, we cannot currently deliver transfer rules for hierarchies. You must create themmanually after you activate the Content.
<i><u>Solution
Call transaction RSA1 (BW Admin. Workbench >> Modeling >> InfoSources).
You can find the 0GLACCEXT InfoObject (Balance Sheet/P&L Statement Item) in the InfoSources tree under the FI-IO application component (Master Data Financial Accounting General).
Connect your SAP R/3 source system using the "Assign DataSource" function in the context menu for the 0GLACCEXT InfoObject. Select the 0GLACCEXT_T011_HIER DataSource.</u></i>
Segment Hierarchy Header
Source system: xxx (your assigned R/3 source system)
DataSource: 0GLACCEXT_T011_HIER Balance Sheet/P&L Statement Item
Transfer method: PSA
Transfer rules tab page
InfoObject >> Field Assignment
InfoObject Description Field
0HIENM Hierarchy name HIENM
0HIER_VERS Hierarchy version VERSION
0DATEFROM Valid-from date DATEFROM
0DATETO Valid-to Date DATETO
Communication structure/transfer rules
InfoObject Description Tp Rule
0HIENM Hierarchy name TS 0HIENM
0HIER_VERS Hierarchy version TS 0HIER_VERS
0DATETO Valid to TS 0DATETO
0DATEFROM Valid from TS 0DATEFROM
0NORESTNODE Non-assigned nodes X -
0STARTLEVEL Start level X -
0NODEPOSIT Node position X -
0ALEAFNODSP Leaf node display X -
0ALEAFNODCH Display changeable X -
TS means transfer "Field from transfer structure".
Segment Hierarchy Nodes
Source system: xxx (your assigned R/3 source system)
DataSource: 0GLACCEXT_T011_HIER Balance Sheet/P&L Item
Transfer method: PSA
Transfer rules tab page
InfoObjekt >> Field Assignment
InfoObject Description Field
0HIER_NODE Name of the hierarchy node NODE NAME
0DATEFROM Valid-from date DATEFROM
0DATETO Valid-to date DATETO
0GLACCEXT BS/P&L item GLACCEXT
0SIGNCH Sign change RSIGN
0BAL_DEPEND Aggregation of balance sheet item: PLUMI
Balance-dependent
Communication structure/transfer rules
InfoObject Description Tp Rule
0HIER_NODE Hierarchy node TS 0HIER_NODE
0SIGNCH Sign change TS 0SIGNCH
0BAL_DEPEND Balance-dependency TS 0BAL_DEPEND
0GLACCEXT BS/P&L item TS 0GLACCEXT
TS means transfer "Field from transfer structure".
Now activate the 0GLACCEXT InfoSource. -
Company code currency for debit and credit information
hi
i am uisng 0fi_ap_4
Debit amount in Company code currency
Credit amount in company code currency
Cash discount amount (Company Currency)
in above cases what fields i need to take form 0fi_ap_4 datasource?
company code currency means will be local currency?Hi Reddy,
True the local currency means the company code currency, because the infoobject 0LOC_CURRCY is liked to the field
LCURR from the source T001-WAERS (T001 is company codes table).
And the related fields for the infoobjects are:
Infoobject Description Field in Datasource Source
0CREDIT_LC Credit amount in local currency DMHAB Calculated
0DEBIT_LC Debit amount in local currency DMSOL Calculated
0DSC_AMT_LC Cash discount amount SKNTO BSIK- SKNTO
Regards.
Yacine.
Edited by: Yacine Bradai on May 5, 2010 3:12 AM
Edited by: Yacine Bradai on May 5, 2010 3:16 AM
Edited by: Yacine Bradai on May 5, 2010 3:17 AM
Edited by: Yacine Bradai on May 5, 2010 3:19 AM
Edited by: Yacine Bradai on May 5, 2010 3:19 AM -
Find the std Business content for these objects in CRM..
Hi,
Can you please help me in finding
To identify the standerd BW extractors in the Business Content.
From the CRM
Business Content for the following objects
Product ( New products in CRM and not in R/3)
Sales Orders à
à Line items.
Quotations CRM only
Billing Documents CRM
Credit Notes
Customers - àNot fully registered " prospects will be in CRM only.
Customers will be transported to R/3
IBASE àMaster Data Item
àContent?
Activities CRM
Please help me how can I find the std Business content for these objects in CRM..CRM Business content objects:
0CRM_LEAD_H - Lead Header (Transactional Data)
0CRM_LEAD_I - Lead Item (Transactional Data)
0CRM_MIG - Mail GUID
Characteristics
InfoObject Description
0CRM_LEAGUI Lead GUID
0STAONESYS0 CRM status life cycle (One Order)
0STAONESYS4 CRM status opportunity/lead (One Order)
0CRM_RCA Catalog
0CRM_RG Code group
0CRM_RCO Code
0CRM_PROSPE Prospect
0BP_CONTPER CRM contact partner
0BP_RESPPER CRM owner
0CRM_SALESP CRM sales partner
0CRM_OBJTYP Business transaction object type
0CRM_ITOBTP CRM item transaction type (object type)
0CRM_MKTELM CRM marketing element
0CRMPLEAGUI CRM preceding lead GUID
0CRM_LEADCR Creation date of the lead
0CRM_OPPGUI GUID of a preceding opportunity
0CRM_OPPCRD Creation date of the opportunity
0CRM_PREOTP Object type of the preceding document
0DIVISION Division
0DISTR_CHAN Distribution channel
0CRM_SRVORG CRM service organization
0CRM_SALOFF Sales office
0CRM_SALORG Sales organization
0CRM_SALGRP Sales group
0CRMSA_OG_R Responsible organizational unit (sales)
0CRMSE_OG_R Responsible organizational unit (service)
0CRM_PRHIER Product category ID
0CRM_PROD CRM product
0CRM_ORDPRD Product name entered
0MATERIAL Material (allocation to R/3)
Time Characteristics
InfoObject Description
0CALDAY Calendar day
0CALMONTH Calendar year/month
0CALQUARTER Calendar year/quarter
0CALYEAR Calendar year
0FISCPER Fiscal year/period
0FISCYEAR Fiscal year
0FISCVARNT Fiscal year variant
Key Figures
InfoObject Description
0CRM_NUMDOC Number of order headers
0CRM_NUMOFI Number of order items
0CRM_LDOQV CRM: Expected order quantity in VME
0CRM_LDOQB CRM: Expected order quantity in BME
0CRM_DURLEA Duration of the lead
0CRM_EXDULD Expected duration of the lead
0CRM_NUMACT Number of activities per lead
0CRM_NUMCHL Number of changes in the qualification level per lead
0CRM_LEAWON Won leads
Units
InfoObject Description
0SALES_UNIT Sales unit
0BASE_UOM Base unit of measure
InfoCube 0CSAL_C01 - CRM Activities.
ODS Object 0SAL_DS01 (ODS for Activities)
Query (technical name) Query (description)
0CSAL_C01_Q0006 Success/Failure Analysis
0CSAL_C01_Q0016 Activity History
0CSAL_C01_Q0002 Intensity of Customer Care (Owner) 12M
InfoCube Opportunities - 0CRM_C04 (SAP BW Business Content)
InfoSources
CRM Opportunities: Header Data - 0CRM_OPPT_H
CRM Opportunities: Item Data - 0CRM_OPPT_I
Query (technical name) Query (description)
0CRM_C04_Q0100 Channel Management Sales Forecast
0CRM_C04_Q001 Win/Loss Analysis for Opportunities
0CRM_C04_Q002 Sales Volume Forecast
0CRM_C04_Q003 Pipeline Analysis per Phase
Hope it will helps you a lot.......... -
Hi guys,
My standard infoobject want to change from Direct update to Flexible Update.Can anybody help them...
Regards
Rams......Hi Ram,
Not sure which BW version you are on,please check the note mentioned below -
As per SAP Note No 511477..Flexible upload for BW3.0B is only possible for
InfoObject Description (Source system type)
0CUSTOMER Customer (SAP R/3)
0VENDOR Vendor (SAP R/3)
0COMP_CODE Company code (SAP R/3)
0MATERIAL Material (SAP R/3)
0SERVICE Service number (SAP R/3)
0MATL_GROUP Material group (SAP R/3)
0PROD_HIER Product hierarchy (SAP R/3)
0BPARTNER Business partner (SAP CRM / EBP)
0CRM_PROD CRM Product (SAP CRM)
0BBP_PROD Product (SAP EBP)
0PROD_CATEG Product category (SAP CRM / EBP)
0APO_PROD APO Product (SAP APO)
0APO_LOCNO APO Location (SAP APO)
0UNSPSC UNSPSC Code (SAP EBP)
0ECLASS EClass (SAP EBP)
VC
Maybe you are looking for
-
WebLogic server is shut down automatically
After i install weblogic6.1 and run default server, I got the fowllowing message and then server is shut down automatically, I tried it days before, and it works, why not work now? Thanks in advance!
-
View History in Photoshop Elements 10
How do I view History of editing in order to make changes in Photoshop 10?
-
IMAC G5 shuts off by itself without showing any errors
My Imac G5 will shut off when it is left in the sleep mode for 2 or more hours. The system will come back on when turned back on and does not show any errors. Everything seems to be running great except for the fact it shuts off by itself. Please Hel
-
Tracing BPS Allocations in a Sequence ...
First off, I'd like to thank you for your contributions, and let you know that I found the discussions on this forum very informative. I appreciate your taking the time to share your experiences I'm working with a client who has been running allocati
-
Vertical pictures become horizontal after being imported
I imported pictures directly from my picture folder. I need the vertical pictures to stay vertical, but many of them, not all of them, become horizontal after being imported into iMovie 06. How do I correct this? Thanks for your help.