How to restrict keyfigures in transfer structure?
hi,
i have 10 key figures(fields) in my data source,but i want to restrict 5 keyfigures of these 10kf (2nd,4th,6th,8th,10th kf's which i want restrict).will be displayed rest of 5 keyfigures. condition should be in transfer structure not in updaterules.i am unable to find the way to get
thanks & regards
venkat
HI Venkat,
As said jayasudha, No need to map the infoobject in the transfer structure. If u r loading the data from R3 then go Extract Structure in rsa6 select ur DS and click on change. In extract structure hide the ur keyfigure.
Thanks
Khaja
Similar Messages
-
How to restrict keyfigures in my bex query which is built of infosets?
Hi all,
How to restrict keyfigures in the query which is built of infosets?
the query display likes
cost taxamount units
1000 100 10
i want my report to be displayed like this
cost taxamount units
100 10 1.
I have used conditions by restricting using units. like
units equal to 1. but still it display like the above one.
can anyone help me on this??
thanxs
harithaHi Haritha,
Do u want to display units 10 as 1?????
If this is the requirement then u can write a new formula by using IF condition.
Khaja -
Copy transfer structure transfer rules from one client to other client
Hi
Our R3 client 100 is mapped to BW client 100.
R3 client 100 is source system in BW.
As the master data is created by users in R3 client 200 we want to get the data from client 200 to BW. We dont want to replicate each datasource and do all stuff form scratch for client 200.
Now the question is as we need to create transfer rules, transfer structure for all master data objects for client 200 in BW.
1. Going to create R3 200 client in BW.--this is possible.
2.Like create a transport connection in BW for client 200 for all master data infoobjects transfer rules transfer structure,process chain, infopackages..etc
3.Do the source system mapping for new client 200.
4.and then execute the process chain..
What are the best ways to achieve this.
creating all transfer structure and transfer rules only for those we are loading daily ..rather than all active ones.. How can I get the list of that master data that is loading daily.. and how easily can I create transfer structure..etc dependent objects in one go than manually.
Any help or thoughts are appreciated..
can anyone throw some light please....Hi,
BW is not client dependent!!! When you sign on to BW, you have the client required. However, this field does not appear in any table (master data, ODS, cubes, whatever).
This means that a same BW server with a single client can have multiple R/3 connections (for multiple R/3 clients).
The database do not care about the client in BW. The data will be consolidated.
So, you do not need any new client in BW, just two R/3 connections for your two clients.
Regards, -
Reg Keyfigures data type in Transfer structure
Hi Guys,
When we create a transfer structure for a falt file source system, keyfigures data type is getting converted into CHAR automatically and even the length is assigned . Whats the reason behind this?? How do we get the lenght of a keyfigure?Hi Reddy,
CSV stands for "Comma Separated Value". This file format is often used to exchange data between disparate applications. The file format, as it is used in Microsoft Excel, has become a pseudo standard throughout the industry, even among non-Microsoft platforms whereas
<u>ASCII codes</u> represent text in computers, communications equipment, and other devices that work with text.
<u>The CSV File Format</u>
Each record is one line ...but
A record separator may consist of a line feed (ASCII/LF=0x0A), or a carriage return and line feed pair (ASCII/CRLF=0x0D 0x0A).
...but: fields may contain embedded line-breaks (see below) so a record may span more than one line.
Fields are separated with commas.
Example John,Doe,120 any st.,"Anytown, WW",08123
Leading and trailing space-characters adjacent to comma field separators are ignored.
So John , Doe ,... resolves to "John" and "Doe", etc. Space characters can be spaces, or tabs.
Fields with embedded commas must be delimited with double-quote characters.
In the above example. "Anytown, WW" had to be delimited in double quotes because it had an embedded comma.
Hope it helps...let me know
regards,
R.Ravi -
Re: How to see transfer structure in sap r/3 system
Hi All,
In generic extraction I have created extract structure ,in the extract structure I have 6 fields but I am trasferring only 4 fields to the BW system ,So it will creates transfer structure in BW System with the 4 fields but when the Transfer structure in sap r/3 generates and how can see the transfer structure in sap r/3 system.I will give full points if i get the correct answer.
Regards,
VenkatHi ,
Data source = extract structure in r/3 system + transfer structure in r/3 system + transfer structure in bw system .
for exmpale you try to extract the following fields
1) vbeln
2) erdat
3) ernam
4)netwr
5)waerk from vbak table but you decided to trasfer only 4 fields expect the erdat in that case
extract structure contains all 5 fields and transfer structure contains 4 fields in BW system expect erdat field,
As far as my knowledge is concern when replicate the data source in bw system and activate the infosource at that time
it will create the transfer structure in r/3 system but I dont know how to see the transfer structure in r/3 system,
please help me in this regard.
Regards,
Venkat -
How to transfer all the transfer structure to new source system ?
Hello
I have created a new source system on my BW system with new RFC connection .
I want to replace all my old transfer structure with old source system to this new system .
can u plz let me know how can i do this ?
Regards,can u plz many help in this ?
-
How to change in Transfer structure
Hi All,
I want change the mapping of one of my info object in transfer structure.
When I am clicking on the change-display button (pen/spec icon),it's not going into change mode & every thing remains disabled.
I tried with SAPALL authorization from BASIS.....still its the same..
Is there any other way ??
Plz suggest.
Regards,
Kironmoy Banerjeehii,
firstly check whether the info object u want to insert is available in ur data source or not.if available then there is no need to insert that info object into the transfer structure.but if not,then u have to first insert the Info object in to the data source,then the info object will itself comes into the transfer structure.
Neha -
I transferred my photos from my PC to my IPOD and IPAD, c. 4000. I thought they would be transferred in the existing folders, all I got was 4000 individual photos, how do I retain the folder structure?
If you are syncing a number of folders from your computer then each folder should get it's own album on the iPad (http://support.apple.com/kb/HT4236) - I assume that you've touched the 'Albums' button at the top of the Photos app so as to view them by album, and not just the Photos 'button'.
You could try closing the Photos app completely and then re-opening it : from the home screen (i.e. not with Photos 'open' on-screen) double-click the home button to bring up the taskbar, then press and hold any of the apps on the taskbar for a couple of seconds or so until they start shaking, then press the '-' in the top left of the Photos app to close it, and touch any part of the screen above the taskbar so as to stop the shaking and close the taskbar.
Another option is to try a reset : press and hold both the sleep and home buttons for about 10 to 15 seconds (ignore the red slider), after which the Apple logo should appear - you won't lose any content, it's the iPad equivalent of a reboot. -
Copy Calculated/Restricted Keyfigures between DIFFERENT InfoProviders
Hello Gurus,
I am struggling with a problem and there doesn't seem to be any clear help on the web. But maybe you can help me.
How can one copy a restricted keyfigure from one infoprovider to another different one when all the infoobjects used for the restricted keyfigure are present in both the providers? (multicubes)
And of course TCode RSZC doesn't work with non-identical infoproviders.
Thank you very much for your help!
MariusThank you Cornelia, but this method was clear for me from the begining... it is not an option though... there are about 30 InfoObjects (and another 40 Multiproviders) so there has to be another way. And there is a way because there is an article on BWExpertOnline which describes an easy method (unfortunately this answer is not worth a thousand dollar subscription for me):
Quick Tip
Copy Queries Between InfoProviders Painlessly
by Joerg Boeke, syskoplan AG BEx Analyzer, InfoCubes, Performance, Query, Debug Mode, InfoProvider
Perhaps, like me, you have spent countless hours successfully creating great queries that contain complex structures for a particular InfoProvider. Then, down the road, you find you need this exact query again for another InfoProvider, but the new InfoProvider has a single characteristic that differs from the one that was the object of your original query. Using SAP transaction RSZC (copying queries between InfoCubes), query definitions can be copied only for use on InfoProviders with the same characteristics. If the key bfigures and characteristics of the new InfoProvider do not match the original 100 percent, this standard method fails.
So close and yet so far, right? Ill show you a way, however, to copy the query definition from one InfoProvider to another, regardless of the characteristics of the new target. This method works with both BW 2.x and 3.x installations.
Source: [http://www.bw-biexpertonline.com/archive/Volume_03_(2005)/Issue_06_(July)/V3I6A2.cfm?session=|http://www.bw-biexpertonline.com/archive/Volume_03_(2005)/Issue_06_(July)/V3I6A2.cfm?session=]
The above mentioned method handles the copying of queries but when we copy the queries we copy the restricted/calculated keyfigures also.
Does anybody know this painless method?
I thank you in advance.
Marius
Edited by: Marius Grunca on Feb 12, 2008 6:35 PM -
Hi ,
in my process chain , it failed due to error: Transfer structure is not active.
How to correc this?
iam using BI 7.0
regards
sidarthaHi Siddartha,
Try to activate the transfer structure using Pogram RS_TRANSTRU_ACTIVATE_ALL in SE 38. Give the Infosource & Source system name there & then execute.
Hope this will help.
~!Dpak -
Transfer structure Activation Problem
hi guys...
i've just installed new bw system and done all post processing steps correctly...
while working in this bw...
if i try to activate any Transfer structure, it is giving an error with the message...
'no ddic tabel /bic/000004000... exists...'
if i go to detailed message...
it is saying that this table shud be created by the system automatically.. otherwise create one in the database utility(se14)...
what does it mean... i'm not understanding what table is this and y i'm being asked for this...???
pl tell me the solution how to rectify this problem...
thank you all
regards
nithinhi...
verson is 30B
if i try to activate again the tabel number in the error message is changing...like /bic/00005000... some number...
is it any problem of any number ranges or what...???
regards..
nithin -
"Transfer structure is not yet active" in each variant of a process chain
I run a big process chain in test environment that I had never run before, but find almost every variant of the process chain show the red error, when I right click the red color variant, get the msg at the status bar that says "Transfer structure is not yet active". Is there a way that can do the mass activation of all master data attributes?
ThanksHi I have the same error message
When I intend running the program to Activate Transfer Structures I get the following error messages
@5C\QError@ Activation not possible: Transfer structure contains invalid field LANGU
@5C\QError@ Transfer structure 0MATERIAL_HIER_AB1 NOT activated successfully Activate manually
@5C\QError@ Activation not possible: Transfer structure contains invalid field NODENAME
@5C\QError@ Transfer structure 0MATERIAL_HIER_AB1 NOT activated successfully Activate manually
@5C\QError@ Activation not possible: Transfer structure contains invalid field LANGU
@5C\QError@ Transfer structure 0MATERIAL_HIER_AB1 NOT activated successfully Activate manually
@5C\QError@ Transfer structure 0MATERIAL_HIER_AB1 NOT activated successfully Activate manually
Please Advise on how to fix it . -
Hello Experts,
While Activating transfer strucutre. Am getting the below error message for some XXX trnasfer structure -
Error while creating table 'EDISEGMENT' entry '/BIC/XXX
Message no. EA201
Diagnosis
An attempt was made to create the entry '/BIC/XXX' in table 'EDISEGMENT'. The attempt failed.
System Response
The operation was canceled.
Procedure
Please check whether the relevant entry already exists.
Can anyone please guide how to step into further
Warm Regards,
AluriHi Aluri,
Try implementing the fixes and the recommendations in "Note 493422 - Inconsistent IDoc segments/transf. structures in srce system"
I think this is very relevant to your problem.
Good luck,
Ali -
Impact of Cost component structure on PA Transfer structure in SAP
Hi All,
We were using a single Operating concern and Controlling area for existing company codes. Now, we got a new company to be created all together a new company with the same chart of accounts.
1. We have created Operating concern, COA, Company code..... and then completed the PA Transfer structure of FI-MM in KEI1
2. I have created a new Costing variant in OKKN
3. I have created the Cost component structure in OKTZ and assigned the new company code to it.
When i go back and checked the PA Transfer structure for FI-MM, i see everything showing as blank.
I have no idea the entire config got deleted.
Do you have any idea how it happens and why it happens please?
Also, will there be any relation b/n OKTZ and KEI1 and sequence to customize?
Hope you understand my query.
Appreciate your early response.
Thanks,
NarasimhuluHi Ravi,
Thanks for your response.
I have created the FI-MM PA transfer structure for the new Controlling area. But after completing the Cost component structure and came back to check the PA Transfer structure, i was surprised since everything to deleted.
I have no idea if we need to follow a sequence while doing these two activities (KEI1 and OKTZ).
Thanks,
Narasimhulu -
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.
Maybe you are looking for
-
If I have an organic shape (ie not a square or circle) and I want to give it an outline, but not use stroke, if I place a copy of the shape below it and expand it then the outlines don't match up, and for very complex shapes it can be time consuming
-
Motion Crashing at start of Project. EVERYTIME
So i was all excited about getting Motion to and using it for my schools football pep rally video's and everytime i open it it crashes. Heres the Log: Date/Time: 2006-09-30 17:04:28.211 -0500 OS Version: 10.4.6 (Build 8I1119) Report Version: 4 Comman
-
I have static text that is justified in a movie clip. The movie clip is being loaded into a scroll pane... but when it loads the text is no longer justified. Does anyone know how I could fix this? Thanks
-
just downloaded captivate 4 when trying to open I get a message saying that I need to install the latest version of flash player...which I already had I have uninstalled and reinstalled I have also made sure that it is enabled and working any ideas?
-
hello 1) i did not find an option to delete files which were sync between my android device and acrobat.com ? 2) what is the URL of the place the files are stored in online with acrobat ? regards