0sold_toparty- 0sales_dist
Hello,
i have sales district as nav attribute of 0customer.
i want to show data for sales district by picking it from customer master in the reports.
The r/3 transactions capture 0sold_toparty (and not 0customer directly).
so i created sales dist as nav attrib of sold to party.
sold to party is (not sure) created by reference with 0customer.
Reports dont show values for sales district field.
can you please suggest?
thanks
Hello,
Just to bring it on top.
i can't see any values for sales dist which is nav attrib of 0sold_to. All my r/3 transactions capture cutomer values in 0sold_to object.
0sold_to is created with reference 0customer.
0customer also has sales dist as nav attrib.
My reports and cubes don't show any values for sales dist. i want sales dist to be picked up from customer master data and displyed in reports.
i have loaded 0customer master data and it(master data for 0customer) shows values for sales dist.
i have not loaded 0sold_to seperately(as it is reference to 0customer).
Please suggest....
thanks
Similar Messages
-
End routine to fill 0PROFIT_CTR
Hi experts,
i am uploading data from DSO TO INFO CUBE. where some of the customers are assigned to PROFIT CENTER in ECC which is coming to DSO and INFO CUBE perfectly, but most of the customers are not assigned to PROFIT CENTER but assigned to SALES DISTRICT.
so whenever the PROFIT CENTER is blank I need to fill the SALES DISTRICT values for the PROFIT CENTER.
from DSO to CUBE profit center is direct mapping, so i want to write a end routine to fill the values of PROFIT CENTER where PROFIT CENTER is Blank.
here is the default code in the end routine
TYPES:
BEGIN OF _ty_s_TG_1,
* InfoObject: 0FISCPER Fiscal year / period.
FISCPER TYPE /BI0/OIFISCPER,
* InfoObject: 0FISCVARNT Fiscal year variant.
FISCVARNT TYPE /BI0/OIFISCVARNT,
* InfoObject: 0LOC_CURRCY Local currency.
LOC_CURRCY TYPE /BI0/OILOC_CURRCY,
* InfoObject: 0DOC_CURRCY Document currency.
DOC_CURRCY TYPE /BI0/OIDOC_CURRCY,
* InfoObject: 0CLEAR_DATE Clearing date.
CLEAR_DATE TYPE /BI0/OICLEAR_DATE,
* InfoObject: 0AC_DOC_TYP Document type.
AC_DOC_TYP TYPE /BI0/OIAC_DOC_TYP,
* InfoObject: 0DOC_DATE Document Date.
DOC_DATE TYPE /BI0/OIDOC_DATE,
* InfoObject: 0POST_KEY Posting key.
POST_KEY TYPE /BI0/OIPOST_KEY,
* InfoObject: 0COMP_CODE Company code.
COMP_CODE TYPE /BI0/OICOMP_CODE,
* InfoObject: 0GL_ACCOUNT G/L Account.
GL_ACCOUNT TYPE /BI0/OIGL_ACCOUNT,
* InfoObject: 0C_CTR_AREA Credit Control Area.
C_CTR_AREA TYPE /BI0/OIC_CTR_AREA,
* InfoObject: 0DUNN_AREA Dunning Area.
DUNN_AREA TYPE /BI0/OIDUNN_AREA,
* InfoObject: 0LAST_DUNN Date of last dunning notice.
LAST_DUNN TYPE /BI0/OILAST_DUNN,
* InfoObject: 0DUNN_BLOCK Dunning block.
DUNN_BLOCK TYPE /BI0/OIDUNN_BLOCK,
* InfoObject: 0DUNN_LEVEL Dunning level.
DUNN_LEVEL TYPE /BI0/OIDUNN_LEVEL,
* InfoObject: 0DUNN_KEY Dunning key.
DUNN_KEY TYPE /BI0/OIDUNN_KEY,
* InfoObject: 0NETDUEDATE Due date for net payment.
NETDUEDATE TYPE /BI0/OINETDUEDATE,
* InfoObject: 0REASON_CDE Difference Reason for Payments.
REASON_CDE TYPE /BI0/OIREASON_CDE,
* InfoObject: 0DSCT_DATE1 Due date for cash discount 1.
DSCT_DATE1 TYPE /BI0/OIDSCT_DATE1,
* InfoObject: 0DSCT_DATE2 Due date for cash discount 2.
DSCT_DATE2 TYPE /BI0/OIDSCT_DATE2,
* InfoObject: 0SP_GL_IND Special General Ledger Indicator.
SP_GL_IND TYPE /BI0/OISP_GL_IND,
* InfoObject: 0BLINE_DATE Baseline Date For Due Date Calculation.
BLINE_DATE TYPE /BI0/OIBLINE_DATE,
* InfoObject: 0PYMT_METH Payment method.
PYMT_METH TYPE /BI0/OIPYMT_METH,
* InfoObject: 0PMNT_BLOCK Payment block key.
PMNT_BLOCK TYPE /BI0/OIPMNT_BLOCK,
* InfoObject: 0PMNTTRMS Terms of Payment Key.
PMNTTRMS TYPE /BI0/OIPMNTTRMS,
* InfoObject: 0CHRT_ACCTS Chart of accounts.
CHRT_ACCTS TYPE /BI0/OICHRT_ACCTS,
* InfoObject: 0ACCT_TYPE Account type.
ACCT_TYPE TYPE /BI0/OIACCT_TYPE,
* InfoObject: 0COUNTRY Country Key.
COUNTRY TYPE /BI0/OICOUNTRY,
* InfoObject: 0DEBITOR Customer Number.
DEBITOR TYPE /BI0/OIDEBITOR,
* InfoObject: 0FI_DOCSTAT Item Status.
FI_DOCSTAT TYPE /BI0/OIFI_DOCSTAT,
* InfoObject: 0FI_SUBSID Account Number of the Branch.
FI_SUBSID TYPE /BI0/OIFI_SUBSID,
* InfoObject: 0PSTNG_DATE Posting date in the document.
PSTNG_DATE TYPE /BI0/OIPSTNG_DATE,
* InfoObject: 0DEB_CRE_LC Amount in Local Currency with +/- Signs.
DEB_CRE_LC TYPE /BI0/OIDEB_CRE_LC,
* InfoObject: 0DISC_BASE Amount eligible for cash discount in docum
*ent currency.
DISC_BASE TYPE /BI0/OIDISC_BASE,
* InfoObject: 0DSC_AMT_LC Cash discount amount in local currency.
DSC_AMT_LC TYPE /BI0/OIDSC_AMT_LC,
* InfoObject: 0DEB_CRE_DC Foreign currency amount with signs (+/-).
DEB_CRE_DC TYPE /BI0/OIDEB_CRE_DC,
* InfoObject: 0DSC_AMT_DC Cash discount amount in document currency
DSC_AMT_DC TYPE /BI0/OIDSC_AMT_DC,
* InfoObject: 0CREDIT_DC Credit amount in foreign currency.
CREDIT_DC TYPE /BI0/OICREDIT_DC,
* InfoObject: 0CREDIT_LC Credit amount in local currency.
CREDIT_LC TYPE /BI0/OICREDIT_LC,
* InfoObject: 0DEBIT_DC Debit amount in foreign currency.
DEBIT_DC TYPE /BI0/OIDEBIT_DC,
* InfoObject: 0DEBIT_LC Debit amount in local currency.
DEBIT_LC TYPE /BI0/OIDEBIT_LC,
* InfoObject: 0NETTAKEN Net period used.
NETTAKEN TYPE /BI0/OINETTAKEN,
* InfoObject: 0INT_CALC_1 Interest Calculation Numerator Days 1 (Ag
*reed).
INT_CALC_1 TYPE /BI0/OIINT_CALC_1,
* InfoObject: 0INT_CALC_2 Interest calculation numerator days 2 (ag
*reed).
INT_CALC_2 TYPE /BI0/OIINT_CALC_2,
* InfoObject: 0INT_CALC_N Interest Calculation Numerator Net (Agree
*d).
INT_CALC_N TYPE /BI0/OIINT_CALC_N,
* InfoObject: 0INT_CALCT1 Interest Calculation Numerator Days 1 (Re
*alized).
INT_CALCT1 TYPE /BI0/OIINT_CALCT1,
* InfoObject: 0INT_CALCT2 Interest Calculation Numerator Days 2 (Re
*alized).
INT_CALCT2 TYPE /BI0/OIINT_CALCT2,
* InfoObject: 0INT_CALCTN Interest Calculation Numerator Net (Reali
*zed).
INT_CALCTN TYPE /BI0/OIINT_CALCTN,
* InfoObject: ZPART_FUN Partner Function.
/BIC/ZPART_FUN TYPE /BIC/OIZPART_FUN,
* InfoObject: ZAC_CLERK Accounting Clerk.
/BIC/ZAC_CLERK TYPE /BIC/OIZAC_CLERK,
* InfoObject: 0PROFIT_CTR Profit Center.
PROFIT_CTR TYPE /BI0/OIPROFIT_CTR,
* InfoObject: 0SALES_DIST Sales District.
SALES_DIST TYPE /BI0/OISALES_DIST,
* InfoObject: 0SALES_OFF Sales Office.
SALES_OFF TYPE /BI0/OISALES_OFF,
* InfoObject: 0SALES_GRP Sales group.
SALES_GRP TYPE /BI0/OISALES_GRP,
* InfoObject: 0RATING Rating.
RATING TYPE /BI0/OIRATING,
* InfoObject: 0CO_AREA Controlling area.
CO_AREA TYPE /BI0/OICO_AREA,
* InfoObject: ZAM_INSUR Amount Insured.
/BIC/ZAM_INSUR TYPE /BIC/OIZAM_INSUR,
* InfoObject: 0CURRENCY Currency key.
CURRENCY TYPE /BI0/OICURRENCY,
* InfoObject: 0CRED_LIMIT Customer's Credit Limit.
CRED_LIMIT TYPE /BI0/OICRED_LIMIT,
* InfoObject: 0RISK_CATEG Credit Management: Risk Class for New Cus
*tomer.
RISK_CATEG TYPE /BI0/OIRISK_CATEG,
* InfoObject: 0CLR_DOC_NO Clearing Document Number.
CLR_DOC_NO TYPE /BI0/OICLR_DOC_NO,
* InfoObject: 0REF_DOC_NO Reference document number.
REF_DOC_NO TYPE /BI0/OIREF_DOC_NO,
* InfoObject: 0INV_DOC_NO Invoice Number.
INV_DOC_NO TYPE /BI0/OIINV_DOC_NO,
* InfoObject: 0DOC_NUMBER Sales document.
DOC_NUMBER TYPE /BI0/OIDOC_NUMBER,
* Field: RECORD.
RECORD TYPE RSARECORD,
END OF _ty_s_TG_1.
TYPES:
_ty_t_TG_1 TYPE STANDARD TABLE OF _ty_s_TG_1
WITH NON-UNIQUE DEFAULT KEY.
*$*$ begin of global - insert your declaration only below this line *-*
... "insert your code here
*$*$ end of global - insert your declaration only before this line *-*
METHODS
new_record__end_routine
IMPORTING
source_segid type rstran_segid
source_record type sytabix
EXPORTING
record_new type sytabix.
METHODS
end_routine
IMPORTING
request type rsrequest
datapackid type rsdatapid
EXPORTING
monitor type rstr_ty_t_monitors
CHANGING
RESULT_PACKAGE type _ty_t_TG_1
RAISING
cx_rsrout_abort.
METHODS
inverse_end_routine
IMPORTING
i_th_fields_outbound TYPE rstran_t_field_inv
i_r_selset_outbound TYPE REF TO cl_rsmds_set
i_is_main_selection TYPE rs_bool
i_r_selset_outbound_complete TYPE REF TO cl_rsmds_set
i_r_universe_inbound TYPE REF TO cl_rsmds_universe
CHANGING
c_th_fields_inbound TYPE rstran_t_field_inv
c_r_selset_inbound TYPE REF TO cl_rsmds_set
c_exact TYPE rs_bool.
ENDCLASS. "routine DEFINITION
Pleae provide me the end routine code.
regards
venuscm
Edited by: venugopal vadlamudi on Sep 7, 2010 1:14 PM
Edited by: venugopal vadlamudi on Sep 7, 2010 1:15 PMhi experts,
i have written the end routine
if not RESULT_PACKAGE is INITIAL.
LOOP AT RESULT_PACKAGE ASSIGNING <RESULT_FIELDS>.
IF <RESULT_FIELDS>-PROFIT_CTR IS INITIAL .
<RESULT_FIELDS>-PROFIT_CTR = <RESULT_FIELDS>-SALES_DIST.
MODIFY RESULT_PACKAGE FROM <RESULT_FIELDS>.
ENDIF.
ENDLOOP.
endif.
but while doing DTP from DSO to CUBE it is giving following error.
Characteristic value '1000 ' of characteristic 0PROFIT_CTR is not ALPHA -converted.
0PROFIT_CTR info object is ALPHA Converted while 0SALES_DISTRICT is not.
pl provide me the solution
regards
venuscm
Edited by: venugopal vadlamudi on Sep 7, 2010 2:55 PM -
Hi,
When i replicated CO-PA data into BI. It created two DS's:
0COPA_RCTY AND 1_CO_PA_XXXXXXX
I created an Infosource and transfer rules for 1_CO_PA_XXXXXXX but there are a few fields missing that i do see in the operating concern such as:
ARTNR=0MATERIAL
KNDNR=0CUSTOMER
BZIRK=0SALES_DIST
Why are these fields not in the Infosource since they are in the operating concern?
Where would they be?
ThanksDelete the data source and then need to re-create using KEB2 transaction. While re-creating the data source use the same old name so that there won't be any changes in the BW side when you need to assign the data source to info-source. Just replicate the new data source in BW side and map the new field in info-source.
(you can also try, goto KE24 and edit the dataaource and add your fields not 100% sure of it works)
how to select fields refer doc:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/fb07ab90-0201-0010-c489-d527d39cc0c6 -
IP: query shows only open request data, when filtered
Hi,
I can see only data of the open request. but it depends on the filter.
I have a real-time provider with closed requests and one open request. (The closed requests come from manually switching between planning and loading mode.) On top there is a multi-provider and aggregation level on top of the multi-provider. the query is defined on the aggregation level.
In the (plan) query I have 0salesorg and 0sales_dist filtered with variables. And both chars as columns.
e.g.:
in the cube I have (salesorg, salesdist, requ.-no., keyfigure):
A, B, Request1, 35
A, B, Request2, 32
Now I filter
0salesorg = A and 0sales_dist = B
==> I can see only the data of the open request, therefore 35.
But with 0salesorg = empty and 0sales_dist = B
==> I see all data, therefore 67.
The only difference between these data rows is the request.
Any ideas? Thanks.
Regards,
LarsHi Lars,
may be you are observing the effect described in note 1179076. Please also delete the OLAP cache for the plan buffer query <PROV>/!!1<PROV> where <PROV> is the technical name of your InfoProvider (MultiProvider or InfoCube) you are using.
Regards,
Gregor -
Ended with return code: === 8 === while doing transports from Dev to Test
Hi Experts,
We are doing transports from BD1 to BQ1 and getting this error message.
Could anyone please let me know why and what would be the solution for the following error message:
Execution of programs after import (XPRA)
Transport request : BD1K900065
System : BQ1
tp path : tp
Version and release: 370.00.09 700
Execution of programs after import (XPRA)
End date and time : 20070803133308
Ended with return code: ===> 8 <===
Thanks in advance.
Best Regards,
Chandu.Raymonds,
There is huge list of errors coming up. Some of them are as below:
Navigation attribute 0SALESORG is missing in characteristic 0PLANT
Navigation attribute 0SALES_DIST is missing in characteristic 0PLANT
Characteristic 0RT_LOCATIO: Referenced characteristic 0PLANT not (actively) available
Attribute 0INT_CUST from characteristic 0SALESORG not (actively) available
Attribute 0CRM_MKTELM from characteristic 0UCCONTRACT not (actively) available
Attribute 0CRM_MKTELM from characteristic 0UCCONTRACT not (actively) available
Hierarchy characteristic 0BPARTNER of characteristic 0UCCONTRACT is not active
Characteristic 0UCOUTLCONT: Referenced characteristic 0UCCONTRACT not (actively) available
Characteristic 0UCOUTLCONT: Referenced characteristic 0UCCONTRACT not (actively) available
Thanks in advance.
Best Regards,
Chandu. -
Error when activate transfer structure
Dear Experts
I Have problem with transfer structure activation with start routine
If I check the start routine it's ok, no error
but if i activate transfer routine, there is an error bellow:
Syntax error "' '" and "TRAN_STRUCTURE" are not comparable in U in row 627 position 2
Message no. RSAA350
Diagnosis
A syntax error occurred.
System Response
Error message "' '" and "TRAN_STRUCTURE" are not comparable in U in line 627
Procedure
Repair your routine.
but if i delete transfer routine, activation it's ok, there is no error
how to activation transfer structure with start routine ?
really appreciate your help
Best Regards
Jeiminghi Sale
Thanks for your reply
how to check if any short dump during activation ?
the start routine only have 547 rows
these are the start routine :
PROGRAM CONVERSION_ROUTINE.
Type pools used by conversion program
TYPE-POOLS: RS, RSARC, RSARR, SBIWA, RSSM.
Declaration of transfer structure (selected fields only)
TYPES: BEGIN OF TRANSFER_STRUCTURE ,
Record number to be filled in case of adding row(s)
to enable 'error handling'
record TYPE rsarecord,
InfoObject ZGECRE: DATS - 000008
ZGECRE TYPE D,
InfoObject ZSALESORG: CHAR - 000004
ZSALESORG(000004) TYPE C,
InfoObject ZBILLNUM: CHAR - 000010
ZBILL_NUM(000010) TYPE C,
InfoObject 0BILL_ITEM: NUMC - 000006
ZBILL_ITEM(000006) TYPE N,
InfoObject 0CREATEDON: DATS - 000008
ZCREATEDON TYPE D,
InfoObject 0CALDAY: DATS - 000008
ZBILL_DATE TYPE D,
InfoObject 0ACT_GI_DTE: DATS - 000008
ZACT_GI_DTE TYPE D,
InfoObject ZCOMMAMT: CURR - 000017
ZCOMMAMT(000009) TYPE P
DECIMALS 000002,
InfoObject ZAPPIT: CHAR - 000004
ZAPPIT(000004) TYPE C,
InfoObject ZGSM: DEC - 000017
ZBASISWGT TYPE P,
InfoObject ZBL_DATE: DATS - 000008
ZBL_DATE TYPE D,
InfoObject ZBILLPR: CURR - 000017
ZBILLPR(000009) TYPE P
DECIMALS 000002,
InfoObject ZBILLPRTO: CURR - 000017
ZBILLPRTON(000009) TYPE P
DECIMALS 000002,
InfoObject ZBILL_TO: CHAR - 000010
ZBILL_TO(000010) TYPE C,
InfoObject ZBP_MT: CURR - 000017
ZBP_MT(000009) TYPE P
DECIMALS 000002,
InfoObject ZBP_UN: CURR - 000017
ZBP_UN(000009) TYPE P
DECIMALS 000002,
InfoObject ZBRAND: CHAR - 000030
ZBRAND(000030) TYPE C,
InfoObject ZCOLOR: CHAR - 000030
ZCOLOR(000030) TYPE C,
InfoObject ZCOMPANY: CHAR - 000004
ZCOMPANY(000004) TYPE C,
InfoObject 0COST: CURR - 000017
ZCOST(000009) TYPE P
DECIMALS 000002,
InfoObject ZCOST_LOC: CURR - 000017
ZCOST_LOC(000009) TYPE P
DECIMALS 000002,
InfoObject ZCOST_USD: CURR - 000017
ZCOST_USD(000009) TYPE P
DECIMALS 000002,
InfoObject 0DOC_CURRCY: CUKY - 000005
ZDOC_CURRCY(000005) TYPE C,
InfoObject : CUKY - 000005
ZGRPCURR(000005) TYPE C,
InfoObject 0CUST_GROUP: CHAR - 000020
ZCUST_GROUP(000020) TYPE C,
InfoObject ZREQ_DATE: DATS - 000008
ZREQ_DATE TYPE D,
InfoObject ZDOC2USD: FLTP - 000016
ZDOC2USD TYPE F,
InfoObject ZFIN_CHG: CURR - 000017
ZFIN_CHG(000009) TYPE P
DECIMALS 000002,
InfoObject ZFOB_UN: CURR - 000017
ZFOB_UN(000009) TYPE P
DECIMALS 000002,
InfoObject ZFRACT: CURR - 000017
ZFRACT(000009) TYPE P
DECIMALS 000002,
InfoObject ZFRACTLOC: CURR - 000017
ZFRACLOC(000009) TYPE P
DECIMALS 000002,
InfoObject ZFRACTUSD: CURR - 000017
ZFRACUSD(000009) TYPE P
DECIMALS 000002,
InfoObject ZFR_COST: CURR - 000017
ZFR_COST(000009) TYPE P
DECIMALS 000002,
InfoObject ZFR_LOC: CURR - 000017
ZFR_LOC(000009) TYPE P
DECIMALS 000002,
InfoObject ZFR_USD: CURR - 000017
ZFR_USD(000009) TYPE P
DECIMALS 000002,
InfoObject 0INCOTERMS: CHAR - 000003
ZINCOTERMS(000003) TYPE C,
InfoObject ZGRAIN: CHAR - 000001
ZGRAIN(000001) TYPE C,
InfoObject 0LOC_CURRCY: CUKY - 000005
ZLOC_CURRCY(000005) TYPE C,
InfoObject ZMFCMILL: CHAR - 000010
ZMFCMILL(000010) TYPE C,
InfoObject ZMTCLASS: CHAR - 000018
ZMTCLASS(000018) TYPE C,
InfoObject ZMATERIAL: CHAR - 000030
ZMATERIAL(000030) TYPE C,
InfoObject ZMILL: CHAR - 000004
ZMILL(000004) TYPE C,
InfoObject ZNFOB_UN: CURR - 000017
ZNFOB_UN(000009) TYPE P
DECIMALS 000002,
InfoObject ZFOBV: CURR - 000017
ZFOBV(000009) TYPE P
DECIMALS 000002,
InfoObject ZNFOBV: CURR - 000017
ZNFOBV(000009) TYPE P
DECIMALS 000002,
InfoObject 0NET_WGT_DL: QUAN - 000017
ZNET_WGT_DL(000009) TYPE P
DECIMALS 000003,
InfoObject ZNWDLKG: QUAN - 000017
ZNWDLKG(000009) TYPE P
DECIMALS 000003,
InfoObject : UNIT - 000003
ZUNIT_KG(000003) TYPE C,
InfoObject ZNO_INV: CHAR - 000001
ZNO_INV(000001) TYPE C,
InfoObject ZDOC_DATE: DATS - 000008
ZDOC_DATE TYPE D,
InfoObject 0INV_QTY: QUAN - 000017
ZINV_QTY(000009) TYPE P
DECIMALS 000003,
InfoObject ZPMNTTRMS: CHAR - 000004
ZPMNTTRMS(000004) TYPE C,
InfoObject ZPO_DATE: DATS - 000008
ZPO_DATE TYPE D,
InfoObject ZPO_NO: CHAR - 000020
ZPO_NO(000020) TYPE C,
InfoObject ZPRTDISCH: CHAR - 000040
ZPRTDISCH(000040) TYPE C,
InfoObject ZPRT_LOAD: CHAR - 000040
ZPRT_LOAD(000040) TYPE C,
InfoObject 0COND_UNIT: CHAR - 000002
ZCOND_UNIT(000002) TYPE C,
InfoObject ZPRODFORM: CHAR - 000002
ZPRODFORM(000002) TYPE C,
InfoObject 0SALES_DIST: CHAR - 000006
ZSALES_DIST(000006) TYPE C,
InfoObject 0DOC_NUMBER: CHAR - 000010
ZDOC_NUMBER(000010) TYPE C,
InfoObject 0S_ORD_ITEM: NUMC - 000006
ZS_ORD_ITEM(000006) TYPE N,
InfoObject ZSLSEMPLY: CHAR - 000010
ZSALESEMPLY(000010) TYPE C,
InfoObject 0SALES_GRP: CHAR - 000003
ZSALES_GRP(000003) TYPE C,
InfoObject 0SALES_OFF: CHAR - 000004
ZSALES_OFF(000004) TYPE C,
InfoObject : CHAR - 000020
ZSALESTYP(000020) TYPE C,
InfoObject 0SALES_UNIT: UNIT - 000003
ZSALES_UNIT(000003) TYPE C,
InfoObject 0NETVAL_INV: CURR - 000017
ZNETVAL_INV(000009) TYPE P
DECIMALS 000002,
InfoObject ZNVI_LOC: CURR - 000017
ZNVI_LOC(000009) TYPE P
DECIMALS 000002,
InfoObject ZNVI_USD: CURR - 000017
ZNVI_USD(000009) TYPE P
DECIMALS 000002,
InfoObject ZSELVIDOC: CURR - 000017
ZSELVIDOC(000009) TYPE P
DECIMALS 000002,
InfoObject ZSELVILOC: CURR - 000017
ZSELVILOC(000009) TYPE P
DECIMALS 000002,
InfoObject ZSELVIUSD: CURR - 000017
ZSELVIUSD(000009) TYPE P
DECIMALS 000002,
InfoObject ZSELLPRTO: CURR - 000017
ZSELLPRTO(000009) TYPE P
DECIMALS 000002,
InfoObject ZSDTGRP: CHAR - 000001
ZSDTGRP(000001) TYPE C,
InfoObject ZSELLPR: CURR - 000017
ZSELLPR(000009) TYPE P
DECIMALS 000002,
InfoObject ZSELV1USD: CURR - 000017
ZSELVI1US(000009) TYPE P
DECIMALS 000002,
InfoObject ZSHIP_TO: CHAR - 000010
ZSHIP_TO(000010) TYPE C,
InfoObject ZSHPCOND: CHAR - 000002
ZSHPCOND(000002) TYPE C,
InfoObject ZSIZE: CHAR - 000030
ZSIZE(000030) TYPE C,
InfoObject ZSOLD_TO: CHAR - 000010
ZSOLD_TO(000010) TYPE C,
InfoObject ZLASTCHG: DATS - 000008
ZSSCHG TYPE D,
InfoObject 0TAX_AMOUNT: CURR - 000017
ZTAX_AMOUNT(000009) TYPE P
DECIMALS 000002,
InfoObject ZDISCAMT: CURR - 000017
ZDISCAMT(000009) TYPE P
DECIMALS 000002,
InfoObject 0GRS_WGT_DL: QUAN - 000017
ZGRS_WGT_DL(000009) TYPE P
DECIMALS 000003,
InfoObject ZTRADING: CHAR - 000010
ZTRADING(000010) TYPE C,
InfoObject ZTT_AMT: CURR - 000017
ZTT_AMT(000009) TYPE P
DECIMALS 000002,
InfoObject 0UNIT_OF_WT: UNIT - 000003
ZUNIT_OF_WT(000003) TYPE C,
InfoObject 0DELIV_NUMB: CHAR - 000010
ZDEL_NUMBER(000010) TYPE C,
InfoObject ZQLTYGR: CHAR - 000001
ZQLTYGR(000001) TYPE C,
InfoObject ZORDCRDT: DATS - 000008
ZORDCRDT TYPE D,
InfoObject ZDSTCTRY: CHAR - 000003
ZDESTCTRY(000003) TYPE C,
InfoObject ZSLSAGNT1: CHAR - 000010
ZSLSAGNT1(000010) TYPE C,
InfoObject ZSLSAGNT2: CHAR - 000010
ZSLSAGNT2(000010) TYPE C,
InfoObject ZBILLTYPE: CHAR - 000004
ZBILL_TYPE(000004) TYPE C,
InfoObject ZCCLDOCNO: CHAR - 000010
ZCCLDOCNO(000010) TYPE C,
InfoObject ZCRTBY: CHAR - 000012
ZCRTBY(000012) TYPE C,
InfoObject ZDOC_TYPE: CHAR - 000004
ZDOC_TYPE(000004) TYPE C,
InfoObject ZMTGROUP: CHAR - 000009
ZMTGROUP(000009) TYPE C,
InfoObject ZPAYER: CHAR - 000010
ZPAYER(000010) TYPE C,
InfoObject ZPLANT2: CHAR - 000004
ZPLANT(000004) TYPE C,
InfoObject ZCCLFLAG: CHAR - 000001
ZCCLFLAG(000001) TYPE C,
InfoObject ZLOADDATE: DATS - 000008
ZLOADDT TYPE D,
InfoObject ZBATCHNO: CHAR - 000010
ZBATCHNO(000010) TYPE C,
InfoObject ZBPO_UN: CURR - 000017
ZBPO_UN(000009) TYPE P
DECIMALS 000002,
InfoObject ZBP_LOC: CURR - 000017
ZBP_LOC(000009) TYPE P
DECIMALS 000002,
InfoObject ZBP_USD: CURR - 000017
ZBP_USD(000009) TYPE P
DECIMALS 000002,
InfoObject ZBP_VAL: CURR - 000017
ZBP_VAL(000009) TYPE P
DECIMALS 000002,
InfoObject ZDISTCHAN: CHAR - 000002
ZDISTCHA(000002) TYPE C,
InfoObject ZHGLVIB: NUMC - 000006
ZHGLVIB(000006) TYPE N,
InfoObject ZINACT: CURR - 000017
ZINACT(000009) TYPE P
DECIMALS 000002,
InfoObject ZINACTLOC: CURR - 000017
ZINACTLOC(000009) TYPE P
DECIMALS 000002,
InfoObject ZINACTUSD: CURR - 000017
ZINACTUSD(000009) TYPE P
DECIMALS 000002,
InfoObject ZMACHID: CHAR - 000001
ZMACHID(000001) TYPE C,
InfoObject ZORDRLDT: DATS - 000008
ZORDRLDT TYPE D,
InfoObject ZDELCRDT: DATS - 000008
ZDELCRDT TYPE D,
InfoObject ZNEGODATE: DATS - 000008
ZNEGODATE TYPE D,
InfoObject ZPPLPRDT: DATS - 000008
ZPPLPRDT TYPE D,
InfoObject ZDELITM: NUMC - 000006
ZS_DEL_ITEM(000006) TYPE N,
InfoObject ZCONTPRSN: CHAR - 000010
ZCONTPRS(000010) TYPE C,
InfoObject ZENDCUST: CHAR - 000010
ZENDCUST(000010) TYPE C,
InfoObject ZDELVDT: DATS - 000008
ZDELVDT TYPE D,
InfoObject ZANFOB: CURR - 000017
ZANFOB(000009) TYPE P
DECIMALS 000002,
InfoObject ZINVNDOC: CURR - 000017
ZNETWR(000009) TYPE P
DECIMALS 000002,
InfoObject ZINVNLOC: CURR - 000017
ZNETWRLOC(000009) TYPE P
DECIMALS 000002,
InfoObject ZINVNUSD: CURR - 000017
ZNETWRUSD(000009) TYPE P
DECIMALS 000002,
InfoObject ZADUTDOC: CURR - 000017
ZADUTDOC(000009) TYPE P
DECIMALS 000002,
InfoObject ZSINTDOC: CURR - 000017
ZSINTDOC(000009) TYPE P
DECIMALS 000002,
InfoObject ZREPOFF2: CHAR - 000010
ZREPOFF(000010) TYPE C,
InfoObject ZMKTSFDOC: CURR - 000017
ZMKTSFDOC(000009) TYPE P
DECIMALS 000002,
InfoObject ZHRSLSEMP: CHAR - 000010
ZHRSLSEMP(000010) TYPE C,
InfoObject ZBOCMDOC: CURR - 000017
ZBOCMDOC(000009) TYPE P
DECIMALS 000002,
InfoObject ZTRDPART2: CHAR - 000010
ZTRDPART(000010) TYPE C,
InfoObject ZFORWAGT: CHAR - 000010
ZFORWAGT(000010) TYPE C,
InfoObject ZCARRNAM: CHAR - 000010
ZCARRNAM(000010) TYPE C,
InfoObject ZACTSHPDT: CHAR - 000010
ZACTSHPDT(000010) TYPE C,
InfoObject ZTKNUM: CHAR - 000010
ZTKNUM(000010) TYPE C,
InfoObject ZFKNUM: CHAR - 000010
ZFKNUM(000010) TYPE C,
InfoObject ZCOFRCUS: CURR - 000017
ZCOFRCOST(000009) TYPE P
DECIMALS 000002,
InfoObject ZCOBLCUS: CURR - 000017
ZCOBLCOST(000009) TYPE P
DECIMALS 000002,
InfoObject ZCOTHCUS: CURR - 000017
ZCOTHCOST(000009) TYPE P
DECIMALS 000002,
InfoObject ZCOWRSKUS: CURR - 000017
ZCOWARSK(000009) TYPE P
DECIMALS 000002,
InfoObject ZCOPEAKUS: CURR - 000017
ZCOPEAK(000009) TYPE P
DECIMALS 000002,
InfoObject ZCODDUUS: CURR - 000017
ZCODDU(000009) TYPE P
DECIMALS 000002,
InfoObject ZCOOTHUS: CURR - 000017
ZCOOTH(000009) TYPE P
DECIMALS 000002,
InfoObject ZCITRCKLC: CURR - 000017
ZCITRUCK(000009) TYPE P
DECIMALS 000002,
InfoObject ZCIHNDLLC: CURR - 000017
ZCIHANDL(000009) TYPE P
DECIMALS 000002,
InfoObject ZCICOOLLC: CURR - 000017
ZCICOOLGL(000009) TYPE P
DECIMALS 000002,
InfoObject ZCISTVDLC: CURR - 000017
ZCISTVDOR(000009) TYPE P
DECIMALS 000002,
InfoObject ZCICRGOLC: CURR - 000017
ZCICARGO(000009) TYPE P
DECIMALS 000002,
InfoObject ZCIWRFGLC: CURR - 000017
ZCIWHARFG(000009) TYPE P
DECIMALS 000002,
InfoObject ZCIFMGTLC: CURR - 000017
ZCIFUMIGT(000009) TYPE P
DECIMALS 000002,
InfoObject ZCIOTHLC: CURR - 000017
ZCIOTH(000009) TYPE P
DECIMALS 000002,
InfoObject ZBOFRCUS: CURR - 000017
ZBOFRCOST(000009) TYPE P
DECIMALS 000002,
InfoObject ZBOBLCUS: CURR - 000017
ZBOBLCOST(000009) TYPE P
DECIMALS 000002,
InfoObject ZBOHNDLUS: CURR - 000017
ZBOHANDL(000009) TYPE P
DECIMALS 000002,
InfoObject ZBOSTRGUS: CURR - 000017
ZBOSTORG(000009) TYPE P
DECIMALS 000002,
InfoObject ZBOTRSHUS: CURR - 000017
ZBOTRNSH(000009) TYPE P
DECIMALS 000002,
InfoObject ZBODDUUS: CURR - 000017
ZBODDU(000009) TYPE P
DECIMALS 000002,
InfoObject ZBOOTHUS: CURR - 000017
ZBOOTH(000009) TYPE P
DECIMALS 000002,
InfoObject ZBITRCKLC: CURR - 000017
ZBITRUCK(000009) TYPE P
DECIMALS 000002,
InfoObject ZBIHNDLLC: CURR - 000017
ZBIHANDL(000009) TYPE P
DECIMALS 000002,
InfoObject ZBIDFEELC: CURR - 000017
ZBIDOCFEE(000009) TYPE P
DECIMALS 000002,
InfoObject ZBISTVDLC: CURR - 000017
ZBISTVDOR(000009) TYPE P
DECIMALS 000002,
InfoObject ZBICRGOLC: CURR - 000017
ZBICARGO(000009) TYPE P
DECIMALS 000002,
InfoObject ZBIWRFGLC: CURR - 000017
ZBIWHARFG(000009) TYPE P
DECIMALS 000002,
InfoObject ZBISTRGLC: CURR - 000017
ZBISTORG(000009) TYPE P
DECIMALS 000002,
InfoObject ZBIFMGTLC: CURR - 000017
ZBIFUMIGT(000009) TYPE P
DECIMALS 000002,
InfoObject ZBIOTHLC: CURR - 000017
ZBIOTH(000009) TYPE P
DECIMALS 000002,
InfoObject ZLFDAT: DATS - 000008
ZLFDAT TYPE D,
InfoObject ZDELAYRS: CHAR - 000004
ZDELAYRS(000004) TYPE C,
InfoObject ZCLEARDT: DATS - 000008
ZCLEAR_DATE TYPE D,
InfoObject ZINV_DUE: DATS - 000008
ZINV_DUE TYPE D,
InfoObject ZBRSLSPR: CHAR - 000010
ZBRSLSPR(000010) TYPE C,
InfoObject ZMLSLSSP: CHAR - 000010
ZMILSLSSP(000010) TYPE C,
InfoObject : CHAR - 000006
ZDISPID(000006) TYPE C,
InfoObject : CHAR - 000006
ZLOAPID(000006) TYPE C,
InfoObject ZOITMFRS: DEC - 000001
ZOITMFRS TYPE P,
InfoObject ZOEACCS: DEC - 000001
ZOEACCS TYPE P,
InfoObject ZINVACCS: DEC - 000001
ZINVACCS TYPE P,
InfoObject ZBILPSTS: DEC - 000001
ZBILPSTS TYPE P,
InfoObject ZDOCPROS: DEC - 000001
ZDOCPROS TYPE P,
InfoObject ZCNTORD: NUMC - 000001
ZCNTORD(000001) TYPE N,
InfoObject ZCNTORDI: DEC - 000001
ZCNTORDI TYPE P,
InfoObject ZTRDPART: CHAR - 000003
ZSOURCE(000003) TYPE C,
InfoObject ZATA: DATS - 000008
ZATA TYPE D,
InfoObject ZRRD: DATS - 000008
ZRRD TYPE D,
InfoObject ZRAD: DATS - 000008
ZRAD TYPE D,
InfoObject ZCUOBJ: NUMC - 000018
ZCUOBJ(000018) TYPE N,
InfoObject ZIDR2USD: FLTP - 000016
ZIDR2USD TYPE F,
InfoObject ZPRCDAT: DATS - 000008
ZEXCRDAT TYPE D,
InfoObject ZNEGOTYP: CHAR - 000003
ZNEGOTYP(000003) TYPE C,
InfoObject ZDLYNRSN: CHAR - 000004
ZDLYNRSN(000004) TYPE C,
InfoObject ZADLYNRS: CHAR - 000070
ZADLYNRS(000070) TYPE C,
InfoObject ZDOCCRDT: DATS - 000008
ZDOCCRDT TYPE D,
InfoObject ZBLEDDDT: DATS - 000008
ZBLEDDDT TYPE D,
InfoObject ZDOCSDDT: DATS - 000008
ZDOCSDDT TYPE D,
InfoObject ZPAIDDOC: CURR - 000017
ZPAIDAMT(000009) TYPE P
DECIMALS 000002,
END OF TRANSFER_STRUCTURE .
Declaration of Datapackage
TYPES: TAB_TRANSTRU type table of TRANSFER_STRUCTURE.
Global code used by conversion rules
$$ begin of global - insert your declaration only below this line -
TABLES: /bic/pzmtclass, /bic/azods_sr00,
/bic/pzsalesorg, /bic/pzbilltype,
/bic/pzdoc_type, /bic/pzpmnttrms,
/bic/pzplant2,
t006.
data : begin of IT_VC occurs 0,
ZSALESORG LIKE /BIC/AZODS_SO00-/BIC/ZSALESORG,
ZDOC_NUMB LIKE /BIC/AZODS_SO00-DOC_NUMBER,
ZDOC_ITEM LIKE /BIC/AZODS_SO00-S_ORD_ITEM,
ZCUOBJ LIKE /BIC/AZODS_SO00-/BIC/ZCUOBJ,
ZATNAM LIKE /BIC/AZODS_VC00-/BIC/ZATNAM,
ZATWRT LIKE /BIC/AZODS_VC00-/BIC/ZATWRT,
end of IT_VC.
DATA: D like SY-DATUM,
l_calmonth(7) type C,
F_V1(16) type P decimals 3,
F_V2(16) type P decimals 3,
F_V3(16) type P decimals 3,
F_TMP(16) type P decimals 3,
f_tmp2(16) type p decimals 2,
slsorg(10) value '0000000000',
uomtmp like t006-MSEHI,
ag_bill like /bic/pzcustomer-accnt_grp,
ag_ship like /bic/pzcustomer-accnt_grp,
shell like /bic/pzcustomer-/bic/zshell,
zflg1 like /bic/pzcustomer-/bic/zflag1,
mtltype like /bic/pzmtclass-matl_type,
mtlclass like /bic/pzmtclass-/bic/zmtclass,
mtlgroup like /bic/pzmtgroup-/bic/ZMTGROUP,
org1 like /bic/pzsalesorg-/bic/zslsorg_1,
vmillalc like /bic/pzsalesorg-/bic/zmillalc,
gecre like /bic/azods_sr00-/bic/zgecre,
mtgrptmp(9) value '000000000',
vmfcmill like /bic/pzmaterial-/bic/zmfcmill,
vsalesorg like /bic/pzplant2-/bic/zsalesorg,
vtmp type I.
$$ end of global - insert your declaration only before this line -
FORM STARTROUTINE
USING G_S_MINFO TYPE RSSM_S_MINFO
CHANGING DATAPAK type TAB_TRANSTRU
G_T_ERRORLOG TYPE rssm_t_errorlog_int
ABORT LIKE SY-SUBRC. "set ABORT <> 0 to cancel datapackage
$$ begin of routine - insert your code only below this line -
DATA: l_s_datapak_line type TRANSFER_STRUCTURE,
l_s_errorlog TYPE rssm_s_errorlog_int.
abort <> 0 means skip whole data package !!!
ABORT = 0.
$$ end of routine - insert your code only before this line -
ENDFORM. -
Mapping Sales dist from customer master to 0SD_C01 infocube
Dear All,
I have a requirment of mapping Sales Dist ( 0SALES_DIST ) from Customer Master ( 0CUST_SALES ) into report based on Infocube Billing Condition Value ( ZSD_C01 ) . i.e. report should show Sales dist data fro customer master and not from transaction data.
The infocube ( ZSD_C01 ) contains sold to party ( 0SOLD_TO ) which can not be mapped to 0CUST_SALES .
Is there any solution for this.Dear Alex ,
When I am doing remodeling to Add 0CUST_SALES in Customer Dimenssion and using 1:1 maping with characteristics of 0SOLD_TO option . system is giving following error.
Characteristic 0SOLD_TO does not have all compoundings of 0CUST_SALES
Since 0CUST_SALES is compounded with Sales Area remodeling doesn't work in spite of having all characteristics of Sales area in the infocube.
Is there any other way to replace the data. -
BI Best Practices for Customization
Dear Experts,
When I am developing BI reports by using mix of Standard BI Content and customized datasources at R/3 side.
In Standard BI Content also I am adding additional columns whereever required.
Now at BI side since I am changing structure/Update rule of cube/ODS, I am copying standard one to Z one.
If I want to make some InfoObjects as Authorization relevant I am copying it and changing that instead of changing original one.
I copied 0SALES_DIST to ZSALESDIS and made it Auth relevant, but I am able to use stadard DS for text (0SALES_DIST_TEXT) in ZSALESDIS which is already used in 0SALES_DIST.
I copied 0CUST_GROUP to ZCUSTGRP and added one attribute to it. I am not able to use 0CUST_GROUP_TEXT in ZCUSTGRP. I intend to use same DS.
0CUST_GROUP is Nav Attr in 0SOLD_TO so I have to copy 0SOLD_TO and use that customized in all my InfoProviders.
Even if I do that I am worried that there will be duplicate data for small small changes.
Can you please help me how to copy and customize the data model without disturbing standard data models.
Regards,
Tech ChetaHi,
BW SAP Retail
http://help.sap.com/saphelp_nw04/helpdata/en/86/39d6386e24f90ae10000000a114084/content.htm
Revaluation at Retail
http://help.sap.com/saphelp_nw04/helpdata/en/8e/65f438c842cc2be10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/73/d26594107711d4af1e080009d2232d/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/35/e58282fe8711d3b49f006094b9301e/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/39/e531c93747da4a8806612212b013b4/content.htm
www.service.sap.com/bi -->>solution detail -->>Industry Portfolios -->> Sap Retail
http://service.sap.com/bi
http://help.sap.com/content/documentation/industry/docu_is_retail.htm
http://help.sap.com/content/documentation/industry/docu_is_retail_retail.htm
http://help.sap.com/content/bestpractices/industry/bestp_industry_retail.htm
Hope this helps,
Regards
CSM reddy -
Transport from bi dev to bi prod - Ended with return code: 8
In transport connection we have collected infocube an its all related objects and created a transport request when moving from dev to prod it is showing this error log file
KBDK900082 HBT-BI HBT-BI/CUBE ZIC_C03/
KBDK900083 HBT-BI Repair
KBDK900084 HBT-BI Development/Correcti
Application components
InfoArea
InfoCube
Data Transfer Process: Active Version
InfoObject
Communication structure
DataSource Replica
InfoPackage
Transfer Rules
InfoSource transaction data
DataStore Object
Routine
DataSource in BW
Communication Structure for Transformation
Transformation
Update rules
Log File: /usr/sap/trans/log/KBDR900082.KBP
Execution of programs after import (XPRA)
Transport request : KBDK900082
System : KBP
tp path : tp
Version and release: 376.01.14 701
Post-import methods for change/transport request: KBDK900082
Post-import method RSOD_SBEL_AFTER_IMPORT started for SBEL L, date and time: 20110907155447
Start of the after-import method for object type(s) SBEL (Metadata Documents)
Post-import method RS_AFTER_IMPORT started for UPDR L, date and time: 20110907155448
Start of the after-import method RS_AREA_AFTER_IMPORT for object type(s) AREA (Activation Mode)
Start of the after-import method RS_APCO_AFTER_IMPORT for object type(s) APCO (Activation Mode)
Start of the after-import method RS_ROUT_AFTER_IMPORT for object type(s) ROUT (Activation Mode)
Start of the after-import method RS_IOBJ_AFTER_IMPORT for object type(s) IOBJ (Activation Mode)
Syntax error Incorrect statament: Expression missing Operand mi in row 20 position 0
Characteristic 0UNLD_PT_WE: Error when activating or checking the transfer routine
Attribute 0UNLD_PT_WE from characteristic 0VENDOR not (actively) available
Characteristic 0VEND_PRIOR: Referenced characteristic 0VENDOR not (actively) available
Characteristic 0VEND_PRIOR: Referenced characteristic 0VENDOR not (actively) available
Attribute 0VENDOR from characteristic 0APO_LOCNO not (actively) available
Attribute 0VENDOR from characteristic 0APO_LOCNO not (actively) available
Characteristic 0APO_PLLOC: Referenced characteristic 0APO_LOCNO not (actively) available
Characteristic 0APO_PLLOC: Referenced characteristic 0APO_LOCNO not (actively) available
Attribute 0APO_LOCNO from characteristic 0APO_RESNAM not (actively) available
Attribute 0VENDOR from characteristic 0APO_RESNAM not (actively) available
Key figure 0APO_RSUTIL: Aggregation reference char.0APO_RSUTIL is not (actively) available
Characteristic 0APO_STORES: Referenced characteristic 0APO_RESNAM not (actively) available
Characteristic 0APO_STORES: Referenced characteristic 0APO_RESNAM not (actively) available
InfoObject 0APO_LOCNO (in compound of characteristic 0APO_SUBLOC) not (act.) available
Characteristic 0APO_VMILOC: Referenced characteristic 0APO_LOCNO not (actively) available
Characteristic 0APO_VMILOC: Referenced characteristic 0APO_LOCNO not (actively) available
Attribute 0VENDOR from characteristic 0BPARTNER not (actively) available
Attribute 0APO_LOCNO from characteristic 0BPARTNER not (actively) available
Attribute 0VENDOR from characteristic 0BPARTNER not (actively) available
Characteristic 0BPARTNER1: Referenced characteristic 0BPARTNER not (actively) available
Characteristic 0BPARTNER1: Referenced characteristic 0BPARTNER not (actively) available
Characteristic 0BPARTNER2: Referenced characteristic 0BPARTNER not (actively) available
Characteristic 0BPARTNER2: Referenced characteristic 0BPARTNER not (actively) available
InfoObject 0BPARTNER1 (in compound of characteristic 0BPRELATION) not (act.) available
InfoObject 0BPARTNER2 (in compound of characteristic 0BPRELATION) not (act.) available
Characteristic 0BP_CONS: Referenced characteristic 0BPARTNER not (actively) available
Characteristic 0BPARTNER2: Referenced characteristic 0BPARTNER not (actively) available
Characteristic 0BPARTNER2: Referenced characteristic 0BPARTNER not (actively) available
InfoObject 0BPARTNER1 (in compound of characteristic 0BPRELATION) not (act.) available
InfoObject 0BPARTNER2 (in compound of characteristic 0BPRELATION) not (act.) available
Characteristic 0BP_CONS: Referenced characteristic 0BPARTNER not (actively) available
Characteristic 0BP_CONS: Referenced characteristic 0BPARTNER not (actively) available
Attribute 0BPARTNER from characteristic 0BP_GRP not (actively) available
Characteristic 0BP_RESPPER: Referenced characteristic 0BPARTNER not (actively) available
Navigation attribute 0BPPOSITION is missing in characteristic 0BPARTNER
Navigation attribute 0USER_NAME is missing in characteristic 0BPARTNER
Navigation attribute 0USER_SYST is missing in characteristic 0BPARTNER Attribute 0CRM_MKTELM from characteristic 0PSGUID not (actively) available
InfoObject 0PLANT (in compound of characteristic 0QUALIFIC) not (act.) available
Characteristic 0RT_CUSTPL: Referenced characteristic 0CUSTOMER not (actively) available
Characteristic 0RT_CUSTPL: Referenced characteristic 0CUSTOMER not (actively) available
Characteristic 0RT_LOCATIO: Referenced characteristic 0PLANT not (actively) available
Navigation attribute 0COMP_CODE is missing in characteristic 0PLANT
Navigation attribute 0COUNTRY is missing in characteristic 0PLANT
Navigation attribute 0COUNTY_CDE is missing in characteristic 0PLANT
Navigation attribute 0DISTR_CHAN is missing in characteristic 0PLANT
Navigation attribute 0PLANTCAT is missing in characteristic 0PLANT
Navigation attribute 0POSTAL_CD is missing in characteristic 0PLANT
Navigation attribute 0PURCH_ORG is missing in characteristic 0PLANT
Navigation attribute 0REGION is missing in characteristic 0PLANT
Navigation attribute 0RMA_FLAG is missing in characteristic 0PLANT
Navigation attribute 0RMA_REFPLT is missing in characteristic 0PLANT
Navigation attribute 0SALESORG is missing in characteristic 0PLANT
Navigation attribute 0SALES_DIST is missing in characteristic 0PLANT
Characteristic 0RT_LOCATIO: Referenced characteristic 0PLANT not (actively) available
Attribute 0INT_CUST from characteristic 0SALESORG not (actively) available
Characteristic 0SOLD_TO: Referenced characteristic 0CUSTOMER not (actively) available
Navigation attribute 0ACCNT_GRP is missing in characteristic 0CUSTOMER
Navigation attribute 0BPARTNER is missing in characteristic 0CUSTOMER
Attribute 0BPARTNER from characteristic 0SOLD_TO not (actively) available
Navigation attribute 0COUNTRY is missing in characteristic 0CUSTOMER
Navigation attribute 0CUST_CLASS is missing in characteristic 0CUSTOMER
Navigation attribute 0CUST_MKT is missing in characteristic 0CUSTOMER
Navigation attribute 0DBDUNS_NUM is missing in characteristic 0CUSTOMER
Navigation attribute 0INDUSTRY is missing in characteristic 0CUSTOMER
Navigation attribute 0KEYACCOUNT is missing in characteristic 0CUSTOMER
Navigation attribute 0NIELSEN_ID is missing in characteristic 0CUSTOMER
Navigation attribute 0OUTL_TYPE is missing in characteristic 0CUSTOMER
regardsHi Krishna,
It seems you have not collected all the info objects and reference info objects into transport request.
Collect the objects into transport request using transport connection in RSA1.
while selecting CUBE, select data flow before, it will collect all the objects into request.
if any business content info objects are there first install from business content and collect into transport request.
Regards,
Venkatesh -
Hi Hi,
I hit an error - 'The argument ' 0 .0' cannot be interpreted as a number' when assigning application structure, line 1, contents "9230000189000001ZF2 LMCNY 20202020080410 ..." when trying out the first loading. Do not know where has gone wrong. Is it the 0 .0 problem? But I checked in RSA3 of the data source and there seems to be no problem.
Has anyone encounter this error before?
Thanks.Hi Sathish,
The folliwing are the mapping. I do not see anything wrong. Please advise if the mapping is logical. Thanks.
VBELN CHAR10 - 0BILL_NUM CHAR10
POSNR NUMC6 - 0BILL_ITEM NUMC6
FKART CHAR4 - 0BILL_TYPE CHAR4
FKDAT DATS - 0BILL_DATE DATS
FKTYP CHAR1 - 0BILL_CAT CHAR1
VBTYP CHAR1 - 0_DOC_CATEG CHAR2
VKORG CHAR4 - 0SALESORG CHAR4
VTWEG CHAR2 - 0DISTR_CHAN CHAR2
BELNR CHAR10 - 0DOC_NUM CHAR10
GJAHR NUMC4 - 0DOC_YEAR NUMC4
KDGRP CHAR2 - ZBUYGRP CHAR2
BZIRK CHAR6 - 0SALES_DIST CHAR6
ERNAM CHAR12 - 0CREATEBY CHAR12
KUNRG CHAR10 - 0PAYER CHAR10
FKSTO CHAR1 - 0AB_FKSTO_L CHAR1
AUBEL CHAR10 - 0DOC_NUMER CHAR10
AUPOS NUMC6 - 0S_ORD_ITEM NUMC 6
MATNR CHAR18 - 0MATERIAL CHAR18
CHARG CHAR10 - 0BATCH CHAR10
PRODH CHAR18 - 0PROD_HIER CHAR 18
WERKS CHAR4 - 0PLANT CHAR4
SHKZG CHAR1 - 0DB_CRD_IND CHAR1
LLAND_AUFT CHAR3 - 0RECIPCNTRY CHAR3
PARVW CHAR2 - 0CPR_PARROL CHAR6
HTL_COLOR CHAR5 - ZCOLOR CHAR5
HTL_EMBOSS CHAR30 - ZEMBOSS CHAR30
HTL_TONE CHAR30 - ZTONE CHAR30
HTL_MARKET CHAR30 - ZMARKET CHAR30
HTL_CONFIG CHAR10 - ZCONFIG CHAR10
HTL_ARTICLE1 CHAR18 - ZARTICLE1 CHAR18
HTL_ARTICLE2 CHAR18 - ZARTICLE2 CHAR18
HTL_SELL_PX_CAT CHAR 30 - ZSPC CHAR30
HTL_STD_FR CHAR15 - ZSTD_FR CHAR 15
HTL_FOAM_CATG CHAR8 - ZFOAM CHAR8
HTL_LEG CHAR18 - ZLEG CHAR18
HTL_PREF_FOAM CHAR30 - ZPREFFOAM CHAR30
HTL_PREF_STD_FR CHAR30 - ZPREF_STD CHAR30
HTL_B_CLOTH_COL CHAR30 - ZCLOTH CHAR30
HTL_GRAIN1 CHAR30 - ZGRAIN1 CHAR30
HTL_GRAIN2 CHAR30 - ZGRAIN2 CHAR30
HTL_VOLTAGE CHAR30 - ZVOLTAGE CHAR30
HTL_ROOT_MODEL CHAR30 - ZRT_MODEL CHAR30
HTL_ROOT_CONFIG CHAR10 - ZRTCONFIG CHAR10
BSARK_E CHAR4 - ZBSARK_E CHAR4
BSTKD_E CHAR35 - ZBSTKD_E CHAR35
POSEX_E CHAR6 - ZPOSEX_E CHAR6
BSARK CHAR4 - ZBSARK CHAR4
BSTKD CHAR35 - ZBSTKD CHAR35
POSEX CHAR6 - ZPOSEX CHAR6
STYPE CHAR1 - ZSSSEATY CHAR1
CONTYP CHAR40 - ZCON_TYPE CHAR40
CUST_GROUP CHAR20 - ZCUSTGRP CHAR20
SORTL CHAR10 - ZSH_SORTL CHAR10
ZSORTL2 CHAR10 - ZSORTL2 CHAR10
ZLAND1 CHAR3 - ZLAND1 CHAR3
ADRNR CHAR10 - 0ADDR_NUMBER CHAR10
LAND1 CHAR3 - 0COUNTRY CHAR3
NAME1 CHAR35 - ZCUSTNAME CHAR35
MAKTX CHAR40 - ZMAT_DESC CHAR40
BEZEI CHAR20 - ZSTATUS CHAR20
ACTIV NUMC2 - ZACTIVE NUMC2
ERDAT DATS - 0CREATEON DATS
ERZET TIMS - 0CREA_TIME TIMS
BUCHK CHAR1 - ZBUCHK CHAR1
NETWR CURR15 - 0NETVAL_INV CURR9
FKIMG QUAN13 - 0INT_QTY QUAN9
KZWI1 CURR15 - 0SUBTOTAL_1 CURR9
KZWI2 CURR15 - 0SUBTOTAL_2 CURR9
KZWI3 CURR15 - 0SUBTOTAL_3 CURR9
KZWI4 CURR15 - 0SUBTOTAL_4 CURR9
BRGEW QUAN15 - 0GRS_WGT_DL QUAN9
NTGEW QUAN15 - 0NET_WGT_DL QUAN9
ZZVOLUM QUAN13 - 0VOLUME QUAN9
HIDES_NUM QUAN15 - ZHIDES QUAN9
NUM_CONTAINER QUAN15 - ZCONTAIN QUAN9
SSEAT QUAN15 - ZSEAT QUAN9
ZKZWI1 CURR13 - ZKZWI1 CURR9
ZKZWI2 CURR13 - ZKZWI2 CURR9
ZKZWI3 CURR12 - ZKZWI3 CURR9
ZKZWI4 CURR13 - ZKZWI4 CURR9
NETPR CURR11 - 0NET_PRICE CURR9
ZKZWI1_UP CURR13 - ZKZWI1_UP CURR9
ZKZWI2_UP CURR13 - ZKZWI2_UP CURR9
ZKZWI3_UP CURR13 - ZKZWI3_UP CURR9
VOLUM QUAN15 - ZVOLUME QUAN9
WAERK CUKY5 - 0DOC_CURRCY CUKY5
VRKME UNIT3 - 0BASE_UOM UNIT3
VRKME UNIT3 - 0SALES_UNIT UNIT3
GEWEI UNIT3 - 0UNIT_OF_WT UNIT3
VOLEH UNIT3 - 0VOLUMEUNIT UNIT3
ZZVOLEH UNIT3 - ZVOLUNIT UNIT3 -
Navigational attribute issue in query
Hi gurus,
Here is a very tricky issue that I am facing. If anyone could please help me with a workaround for the same.
I have an infoObject called ZDIV_CUS which is basically 0CUSTOMER with 0DIVISION compounded to it. Hence, when I load data into ZDIV_CUS, I would have one record for a unique combination of customer and division. In functional words, I would have one customer maintained for multiple divisions. ZDIV_CUS also has other navigational attributes as 0SALES_OFF, 0SALES_DIST & 0SALES_GRP. Also, I have 0MATERIAL, which has 0DIVISION as a navigational attribute in my cube.
Hence the master data for ZDIV_CUS looks as follows -
0DIVISION 0CUSTOMER 0SALES_OFF 0SALES_GRP 0SALES_DIST
01 100000 L001 L01 L010100
02 100000 L005 L08 L020150
01 100001 L001 L01 L050150
03 100001 L005 L02 L052542
The transactional data in my cube is as follows -
0MATERIAL 0CUSTOMER 0DIVISION 0SALES_OFF 0NET_SALES 0MATERIAL_DIVISION (Material master div)
102152 100000 01 L002 110000 02
102545 100001 02 L002 12000000 02
The above data is all transactional except for 0MATERIAL_DIVISION which comes from material division.
My query is built in such a way that the division comes from 0MATERIAL (restricted to variable in the selection screen). ZDIV_CUS and its navigational attributes are being used in my query. The initial display is shown as per ZDIV_CUS_0SALES_OFF (i.e. sales office from ZDIV_CUS)
The problem is that say for eg for the above mentioned scenario, the user executes the query for division 01 and the below mentioned output comes up -
0MATERIAL_DIVISION ZDIV_CUS 0MATERIAL ZDIV_CUS_0SALES_OFF 0NET_SALES
02 100000 102152 L001 110000
If we take a closer look, we would know that ZDIV_CUS_0SALES_OFF should pick up value L005 and not L001 since the division for which the query is run is 0MATERIAL_DIVISION and not 0DIVISION.
Request help to resolve the abovementioned issue.
Thank you,
SreeCan any one answer for Issue-2. Even I am also facing the same.
Thanks in Advance. -
COMM_SRTUCTURE is uknown when migrating data flow bw 3.x to 7.4
Dear ALL,
2LIS_13_VDHDR data flow migrating 3.x to 7.x , ABAP syntax error COMM_STRUCTURE is unknown infosoure transformation level, present we are using 7.4 sp5 . after migration ABAP code
TYPES:
BEGIN OF _ty_s_TG_1_full,
* InfoObject: 0CHNGID Change Run ID.
CHNGID TYPE /BI0/OICHNGID,
* InfoObject: 0RECORDTP Record type.
RECORDTP TYPE /BI0/OIRECORDTP,
* InfoObject: 0REQUID Request ID.
REQUID TYPE /BI0/OIREQUID,
* InfoObject: 0CALDAY Calendar Day.
CALDAY TYPE /BI0/OICALDAY,
* InfoObject: 0CALMONTH Calendar Year/Month.
CALMONTH TYPE /BI0/OICALMONTH,
* InfoObject: 0CALWEEK Calendar year / week.
CALWEEK TYPE /BI0/OICALWEEK,
* InfoObject: 0FISCPER Fiscal year / period.
FISCPER TYPE /BI0/OIFISCPER,
* InfoObject: 0FISCVARNT Fiscal year variant.
FISCVARNT TYPE /BI0/OIFISCVARNT,
* InfoObject: 0BILLTOPRTY Bill-to party.
BILLTOPRTY TYPE /BI0/OIBILLTOPRTY,
* InfoObject: 0COMP_CODE Company code.
COMP_CODE TYPE /BI0/OICOMP_CODE,
* InfoObject: 0DISTR_CHAN Distribution Channel.
DISTR_CHAN TYPE /BI0/OIDISTR_CHAN,
* InfoObject: 0DOC_CATEG Sales Document Category.
DOC_CATEG TYPE /BI0/OIDOC_CATEG,
* InfoObject: 0PLANT Plant.
PLANT TYPE /BI0/OIPLANT,
* InfoObject: 0SALESORG Sales Organization.
SALESORG TYPE /BI0/OISALESORG,
* InfoObject: 0SALES_GRP Sales group.
SALES_GRP TYPE /BI0/OISALES_GRP,
* InfoObject: 0SALES_OFF Sales Office.
SALES_OFF TYPE /BI0/OISALES_OFF,
* InfoObject: 0SHIP_TO Ship-To Party.
SHIP_TO TYPE /BI0/OISHIP_TO,
* InfoObject: 0SOLD_TO Sold-to party.
SOLD_TO TYPE /BI0/OISOLD_TO,
* InfoObject: 0VERSION Version.
VERSION TYPE /BI0/OIVERSION,
* InfoObject: 0VTYPE Value Type for Reporting.
VTYPE TYPE /BI0/OIVTYPE,
* InfoObject: 0DIVISION Division.
DIVISION TYPE /BI0/OIDIVISION,
* InfoObject: 0MATERIAL Material.
MATERIAL TYPE /BI0/OIMATERIAL,
* InfoObject: 0SHIP_POINT Shipping point.
SHIP_POINT TYPE /BI0/OISHIP_POINT,
* InfoObject: 0PAYER Payer.
PAYER TYPE /BI0/OIPAYER,
* InfoObject: 0DOC_CLASS Document category /Quotation/Order/Deliver
*y/Invoice.
DOC_CLASS TYPE /BI0/OIDOC_CLASS,
* InfoObject: 0DEB_CRED Credit/debit posting (C/D).
DEB_CRED TYPE /BI0/OIDEB_CRED,
* InfoObject: 0SALESEMPLY Sales Representative.
SALESEMPLY TYPE /BI0/OISALESEMPLY,
* InfoObject: 0SUBTOT_1S Subtotal 1 from pricing proced. for condit
*ion in stat. curr..
SUBTOT_1S TYPE /BI0/OISUBTOT_1S,
* InfoObject: 0SUBTOT_2S Subtotal 2 from pricing proced. for condit
*ion in stat. curr..
SUBTOT_2S TYPE /BI0/OISUBTOT_2S,
* InfoObject: 0SUBTOT_3S Subtotal 3 from pricing proced.for conditi
*on in stat. curr..
SUBTOT_3S TYPE /BI0/OISUBTOT_3S,
* InfoObject: 0SUBTOT_4S Subtotal 4 from pricing proced. for condit
*ion in stat. curr..
SUBTOT_4S TYPE /BI0/OISUBTOT_4S,
* InfoObject: 0SUBTOT_5S Subtotal 5 from pricing proced. for condit
*ion in stat. curr..
SUBTOT_5S TYPE /BI0/OISUBTOT_5S,
* InfoObject: 0SUBTOT_6S Subtotal 6 from pricing proced. for condit
*ion in stat. curr..
SUBTOT_6S TYPE /BI0/OISUBTOT_6S,
* InfoObject: 0OPORDQTYBM Open orders quantity in base unit of meas
*ure.
OPORDQTYBM TYPE /BI0/OIOPORDQTYBM,
* InfoObject: 0OPORDVALSC Net value of open orders in statistics cu
*rrency.
OPORDVALSC TYPE /BI0/OIOPORDVALSC,
* InfoObject: 0QUANT_B Quantity in base units of measure.
QUANT_B TYPE /BI0/OIQUANT_B,
* InfoObject: 0DOCUMENTS No. of docs.
DOCUMENTS TYPE /BI0/OIDOCUMENTS,
* InfoObject: 0DOC_ITEMS Number of Document Items.
DOC_ITEMS TYPE /BI0/OIDOC_ITEMS,
* InfoObject: 0NET_VAL_S Net value in statistics currency.
NET_VAL_S TYPE /BI0/OINET_VAL_S,
* InfoObject: 0COST_VAL_S Cost in statistics currency.
COST_VAL_S TYPE /BI0/OICOST_VAL_S,
* InfoObject: 0GR_WT_KG Gross weight in kilograms.
GR_WT_KG TYPE /BI0/OIGR_WT_KG,
* InfoObject: 0NT_WT_KG Net weight in kilograms.
NT_WT_KG TYPE /BI0/OINT_WT_KG,
* InfoObject: 0VOLUME_CDM Volume in cubic decimeters.
VOLUME_CDM TYPE /BI0/OIVOLUME_CDM,
* InfoObject: 0HDCNT_LAST Number of Employees.
HDCNT_LAST TYPE /BI0/OIHDCNT_LAST,
* InfoObject: 0CRM_PROD Product.
CRM_PROD TYPE /BI0/OICRM_PROD,
* InfoObject: 0CP_CATEG Category.
CP_CATEG TYPE /BI0/OICP_CATEG,
* InfoObject: 0FISCYEAR Fiscal year.
FISCYEAR TYPE /BI0/OIFISCYEAR,
* InfoObject: 0BP_GRP BP: Business Partner Group (from Hierarchy).
BP_GRP TYPE /BI0/OIBP_GRP,
* InfoObject: 0STAT_CURR Statistics Currency.
STAT_CURR TYPE /BI0/OISTAT_CURR,
* InfoObject: 0BASE_UOM Base Unit of Measure.
BASE_UOM TYPE /BI0/OIBASE_UOM,
* InfoObject: 0PROD_CATEG Product Category.
PROD_CATEG TYPE /BI0/OIPROD_CATEG,
* InfoObject: 0VOLUME Volume.
VOLUME TYPE /BI0/OIVOLUME,
* InfoObject: 0VOLUMEUNIT Volume unit.
VOLUMEUNIT TYPE /BI0/OIVOLUMEUNIT,
* InfoObject: 0FISCPER3 Posting period.
FISCPER3 TYPE /BI0/OIFISCPER3,
* InfoObject: 0SALES_DIST Sales District.
SALES_DIST TYPE /BI0/OISALES_DIST,
* InfoObject: 0BILL_TYPE Billing type.
BILL_TYPE TYPE /BI0/OIBILL_TYPE,
* InfoObject: 0MOVE_PLANT Receiving Plant/Issuing Plant.
MOVE_PLANT TYPE /BI0/OIMOVE_PLANT,
* InfoObject: 0SHIP_COND Shipping conditions.
SHIP_COND TYPE /BI0/OISHIP_COND,
* InfoObject: 0AB_RFBSK Status for Transfer to Accounting.
AB_RFBSK TYPE /BI0/OIAB_RFBSK,
* InfoObject: 0AB_FKSTO Indicator: Document Is Cancelled.
AB_FKSTO TYPE /BI0/OIAB_FKSTO,
* InfoObject: 0CUST_GRP5 Customer Group 5.
CUST_GRP5 TYPE /BI0/OICUST_GRP5,
* InfoObject: ZCU_COND1 Constomer Condition Group 1.
/BIC/ZCU_COND1 TYPE /BIC/OIZCU_COND1,
* InfoObject: ZCU_COND2 Customer Condition Group 2.
/BIC/ZCU_COND2 TYPE /BIC/OIZCU_COND2,
* InfoObject: ZBATCHCD Batch Code.
/BIC/ZBATCHCD TYPE /BIC/OIZBATCHCD,
* InfoObject: 0BATCH Batch number.
BATCH TYPE /BI0/OIBATCH,
* InfoObject: ZBATCH Batch number.
/BIC/ZBATCH TYPE /BIC/OIZBATCH,
* Field: RECORD Data record number.
RECORD TYPE RSARECORD,
END OF _ty_s_TG_1_full.
* Additional declaration for update rule interface
DATA:
MONITOR type standard table of rsmonitor WITH HEADER LINE,
MONITOR_RECNO type standard table of rsmonitors WITH HEADER LINE,
RECORD_NO LIKE SY-TABIX,
RECORD_ALL LIKE SY-TABIX,
SOURCE_SYSTEM LIKE RSUPDSIMULH-LOGSYS.
* global definitions from update rules
* TABLES: ...
DATA: IN TYPE F,
OUT TYPE F,
DENOM TYPE F,
NUMER TYPE F.
* Def. of 'credit-documents': following doc.categ. are 'credit docs'
* reversal invoice (N)
* credit memo (O)
* internal credit memo (6)
* Credit-documents are delivered with negative sign. Sign is switched
* to positive to provide positive key-figures in the cube.
* The combination of characteristics DE_CRED and DOC-CLASS provides
* a comfortable way to distinguisch e.g. positive incoming orders or
* order returns.
* Def. der 'Soll-Dokumente': folgende Belegtypen sind 'Soll-Belege'
* Storno Rechnung (N)
* Gutschrift (O)
* Interne Verrechn. Gutschr. (6)
* Soll-Dokumente werden mit negativem Vorzeichen geliefert. Um die Kenn-
* zahlen positiv in den Cube zu schreiben, wird das Vorzeich. gedreht
* Die Kombination der Merkmale DEB_CRED und DOC-CLASS gibt Ihnen die
* Möglichkeit schnell z.B. zwischen Auftrags-Eingang oder Retouren zu
* unterscheiden.
DATA: DEB_CRED(3) TYPE C VALUE 'NO6'.
FORM routine_0002
TABLES
P_MONITOR structure rsmonitor
CHANGING
RESULT TYPE _ty_s_TG_1_full-DOCUMENTS
RETURNCODE LIKE sy-subrc
ABORT LIKE sy-subrc
RAISING
cx_sy_arithmetic_error
cx_sy_conversion_error.
* init variables
* fill the internal table "MONITOR", to make monitor entries
CLEAR RESULT.
RESULT = COMM_STRUCTURE-NO_INV.
IF COMM_STRUCTURE-DOC_CATEG CA DEB_CRED.
RESULT = RESULT * ( -1 ).
ENDIF.
RETURNCODE = 0.
p_monitor[] = MONITOR[].
CLEAR:
MONITOR[].
ENDFORM. "routine_0002
FORM routine_0003
TABLES
P_MONITOR structure rsmonitor
CHANGING
RESULT TYPE _ty_s_TG_1_full-DEB_CRED
RETURNCODE LIKE sy-subrc
ABORT LIKE sy-subrc
RAISING
cx_sy_arithmetic_error
cx_sy_conversion_error.
* init variables
* fill the internal table "MONITOR", to make monitor entries
IF COMM_STRUCTURE-DOC_CATEG CA DEB_CRED.
RESULT = 'C'.
ELSE.
RESULT = 'D'.
ENDIF.
RETURNCODE = 0.
p_monitor[] = MONITOR[].
CLEAR:
MONITOR[].
ENDFORM.
Error:
E:Field "COMM_STRUCTURE-NO_INV" is unknown. It is neither in one of the
specified tables nor defined by a "DATA" statement. "DATA" statement.
communication structure chaged to sours fields but no uses , please suggest how can i proceed , Thanks in Advance immediate replay
Thanks & Regards
Ramesh GHi Gareth,
You have two options:
1. Transport from BW 3.1 to BI 7.0. You'll need to create a transport route between both systems. This may cause you some troubles in the future when you want to modify the objects you transported.
2. As there are few objects, you can use XML export utility from Transport connection. There, you make an XML file with the objects you need to transport. One thing that you may take care of, in this option, is that the business content objects you are exporting need to be activated in the destination system. Another problem is that querys are not exported.
Since it's only a cube, maybe you can create the objects manually. Look that in BI 7.0 there are several new functionalities, i don't know how transport or xml export would work.
Hope this helps.
Regards,
Diego -
Objectlevel Security in SAP BI
Hi Gurus,
Implementation of Object level security in BI system. Customer is looking to Implement BI security model for a new piece of functionality that they are setting up in BI (Commissions processing) specifically in the area of SD (Sales Distict, Office, Group, etc.).
Kindly suggest me how do i apply Object level security in BI for large number of People.
I have 3 characteristics to Restrict in Analysis Authorization.
0SALES_DIST: 300001, 300002, 300003, 300004
0SALES_OFF: 3010, 3011, 3012, 3020, 3021, 3022
0SALES_GRP: 3AA ,3AB, 3AC, 3AF, 3AG, 3AH
Kindly suggest me the best method to Implement. System is BI 7.0.Hi Syed,
Analaysis authorizations are more flexible than Hirerachy authorizations.
However, the solution is simple. You doesn't require to create 100s of Analysis authorization and can use the user exits, or the variables instead. The below articles provides you detailed information on implementing them, which means you can achieve with a single anaysis authorization
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/9000928e-dd3d-2e10-9ca1-a00f249305b7?quicklink=index&overridelayout=true
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b0b3fb3f-a21c-2e10-3a9c-efc3e59996a8?quicklink=index&overridelayout=true
Regards,
Raghu -
HOW TO USE AN EXISTING HIERARCHY
Hi friends, I have the hierarchy 0SALES_OFF (Sales Office)
The levels in this Hierarchy are ZZONE, 0SALES_ORG, 0SALES_DIST, 0SALES_OFF
Now, i want this hierarchy to be extended to one more level that is 0CUSTOMER at the bottom.
Also 0SALES_OFF is an attribute of 0CUSTOMER.
We have to give the 0SALES_OFF Hierarchy to the 0CUSTOMER so that it will be like
ZZONE, 0SALES_ORG, 0SALES_DIST, 0SALES_OFF, 0CUSTOMER
I hope u understood the requirement
what i require is to link the Sales office Hierarchy to the 0Customer so that it will be fullfilled
CAN ANYBODY HELP ME REGARDING THID URGENT ISSUE.Unfortunately you have 2 options only:-)
- Either maintain it Manually through RSH1
- Maintain your Hierarchy in a Flat File and load your hierarchy through Flat File. This option may be easier if you maintain an Excel file for the hierarchy and generate a CSV file out of it to load it as a Flat File. Only difficulty you might face is to follow the format. You can download your existing hierarchy on a Flat File, modify it and reload it. Check the following link
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/0403a990-0201-0010-38b3-e1fc442848cb
I can't see any other options.
Regards
Anujit Ghosh -
Hi,
I load the master data for Sales District, I got only 4 records in the 0SALES_DIST (Object).
When I check the datasource I have 9 records and in PSA 7 records.
IN R/3
000001 DE Bezirk Nord
000002 DE Bezirk Süd
000001 EN Northern region
000002 EN Southern region
CENTRE EN Lower North Island
NORTH EN Upper North Island
SOUTH EN South Island
000001 ES Zona Norte
000002 ES Zona Sur
IN PSA
000001 DE Bezirk Nord
000002 DE Bezirk Süd
000001 EN Northern region
000002 EN Southern region
CENTRE EN Lower North Island
NORTH EN Upper North Island
SOUTH EN South Island
In the Object
000001 EN Northern region
000002 EN Southern region
CENTRE EN Lower North Island
NORTH EN Upper North Island
SOUTH EN South Island
Please help to get all recordsRobert,
Unflag 'language-dependent text' manually in InfoObject maintenance in the BW-system (RSD1) and activate the InfoObject. Unflaging 'language-dependent text' is an incompatible change (Changes in key of a table): data in table /BI0/T<infoobject> will get lost.
If you have already loaded text data you have to delete this text data before activation and reload the text data after activation again.
Also refer to note 715 687.Let me know if this information helps you.
thanks,
@P..
Maybe you are looking for
-
Dacf; imageControl; doesn't save
JDEV 3.2/JDK 1.3 I set up a table in the database, with a nice LONG RAW column. I hooked in an entity object, a view object and a rowsetinfo. Cool. Set up a frame with a imagecontrol mapped to the rowsetinfo attribute (LONGVARBINARY). Executed it...
-
How to index array in a for loop
i'm connecting from variant-to-data function to an index array function inside a for_loop (refer to attachment). the data-type wire got converted from Table(2-D array) to Table(1-D array). How do I keep it from converting to 1-D array? Attachments:
-
Through transaction FBL1N I am viewing open vendor line items. There is an item that has been blocked due to a duplicate invoice check. How do I determine the original document that this item is a duplicate of? Thanks - points will be rewarded.
-
WRT310N and general LAN questions
I am trying to set up a music studio LAN in my home, and I just bought a WRT310N which I am hoping will help me but I'm not sure now. I have a Mac PowerBook G4 and a Dell WindowsXP from 2003 that doesn't have built in wireless, so I've been using a L
-
Windows 8.1 Installation error
When trying to install windows 8.1 update I am getting an error saying the reserved drive space cant be changed. Can anyone suggest how to avoid this?