Dump while pulling delta with 2LIS_05_QVUDN datasource
Hell All,
We are getting dump (attached) in delta extraction to BW using 2LIS_05_QVUDN datasource. We have analyzed it byt we dont find a good clue.
Please advice,
Runtime Errors RAISE_EXCEPTION
Date and Time 17.09.2009 05:18:14
|Short text |
| Exception condition "DB_CONNECTION_ERROR" raised. |
|What happened? |
| The current ABAP/4 program encountered an unexpected |
| situation. |
|What can you do? |
| Note down which actions and inputs caused the error. |
| |
| |
| To process the problem further, contact you SAP system |
| administrator. |
| |
| Using Transaction ST22 for ABAP Dump Analysis, you can look |
| at and manage termination messages, and you can also |
| keep them for a long time. |
|Error analysis |
| A RAISE statement in the program "SAPLSTD9" raised the exception |
| condition "DB_CONNECTION_ERROR". |
| Since the exception was not intercepted by a superior |
| program, processing was terminated. |
| |
| Short description of exception condition: |
| |
| |
| For detailed documentation of the exception condition, use |
| Transaction SE37 (Function Library). You can take the called |
| function module from the display of active calls. |
| - |
|How to correct the error |
| |
| If the error occures in a non-modified SAP program, you may be able to |
| find an interim solution in an SAP Note. |
| If you have access to SAP Notes, carry out a search with the following |
| keywords: |
| |
| "RAISE_EXCEPTION" " " |
| "SAPLSTD9" or "LSTD9U09" |
| "DB_CONNECT" |
| |
| or |
| |
| "SAPLSTD9" "DB_CONNECTION_ERROR" |
| |
| or |
| |
| "RSORACOL " "DB_CONNECTION_ERROR" |
| If you cannot solve the problem yourself and want to send an error |
| notification to SAP, include the following information: |
| |
| 1. The description of the current problem (short dump) |
| |
| To save the description, choose "System->List->Save->Local File |
| (Unconverted)". |
| |
| 2. Corresponding system log |
| |
| Display the system log by calling transaction SM21. |
| Restrict the time interval to 10 minutes before and five minutes |
| after the short dump. Then choose "System->List->Save->Local File |
| (Unconverted)". |
| |
| 3. If the problem occurs in a problem of your own or a modified SAP |
| program: The source code of the program |
| In the editor, choose "Utilities->More |
| Utilities->Upload/Download->Download". |
| |
| 4. Details about the conditions under which the error occurred or which |
| actions and input led to the error. |
| |
|
|Information on where terminated |
| Termination occurred in the ABAP program "SAPLSTD9" - in "DB_CONNECT". |
| The main program was "RSORACOL ". |
| |
| In the source code you have the termination point in line 80 |
| of the (Include) program "LSTD9U09". |
| The program "SAPLSTD9" was started as a background job. |
| Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR" |
| Job Initiator.. "DDIC" |
| Job Number..... 03512600 |
|Source Code Extract |
|Line |SourceCde |
|
| 59|*&---------------------------------------------------------------------* |
| 60|*& Form db_connect |
| 61|*&---------------------------------------------------------------------* |
| 62|* text |
| 63|*----------------------------------------------------------------------* |
| 64|* -->CON_NAME text |
| 65|*----------------------------------------------------------------------* |
| 66|FORM db_connect USING con_name. |
| 67| CHECK con_name <> 'DEFAULT'. |
| 68| EXEC SQL. |
| 69| set connection :con_name |
| 70| ENDEXEC. |
| 71| IF sy-subrc <> 0. |
| 72| EXEC SQL. |
| 73| connect to :con_name |
| 74| ENDEXEC. |
| 75| IF sy-subrc <> 0. |
| 76| EXEC SQL. |
| 77| connect to :con_name as :con_name |
| 78| ENDEXEC. |
| 79| IF sy-subrc <> 0. |
|>>>>>| RAISE DB_CONNECTION_ERROR. |
| 81| EXIT. |
| 82| ENDIF. |
| 83| ENDIF. |
| 84| ENDIF. |
| 85|ENDFORM. "db_connect |
| 86| |
| 87|*&---------------------------------------------------------------------* |
| 88|*& Form db_disconnect |
| 89|*&---------------------------------------------------------------------* |
| 90|* text |
| 91|*----------------------------------------------------------------------* |
| 92|* -->CON_NAME text |
| 93|*----------------------------------------------------------------------* |
| 94|FORM db_disconnect USING con_name. |
| 95| CHECK con_name <> 'DEFAULT'. |
| 96| EXEC SQL. |
| 97| set connection default |
| 98| ENDEXEC. |
| 99|ENDFORM. "db_disconnect |
Hey when u getting this dump ??
after clicking on info pkg or some where else ??
Tell me ..
Ankit
Similar Messages
-
Short Dump while loading Delta from ODS to ODS
Hi Experts,
I have run into a short dump error while loading delta from one ODS to another via a process chain.
Following is the error message:
Error analysis
Short text of error message:
Request 0000259294 is not completely activated. Please activate it again
Technical information about the message:
Diagnosis
Activation of request 0000259294 has terminated, or is not yet
complete.
System response
Procedure
If the process has terminated, all of the requests that the system
was unabe to activate in the most recent activation process have to
be reactivated before the new requests can be activated.
If you are not able to carry out this activation step, delete the
relevant requests from the administration of the ODS object (on the
Requests tabstrip).
Procedure for System Administration
Message classe...... "RSM1"
Number.............. 180
Variable 1.......... 0000259294
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
Variable 3.......... " "
Variable 4.......... " "
Can someone help me resolve this?
Thank youCheck the status of request SID 259294 in ODS, whether the Activation got completed or not. If not wait till the activation completes.
If there is any problem in the activation process, correct that complete the activation process and load the ne request that you want to load..
Regards
VJ -
Short dump while PO creation with Tax Code
we are facing problem while creation PO, while providing the Tax code(Example V0), its going for short dump, check the below
the program SAPLV61Z and
The exception must either be prevented, caught within the procedure
"SEL_KONDTAB"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
Check the field names in the SELECT clause.
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"SAPSQL_INVALID_FIELDNAME" CX_SY_DYNAMIC_OSQL_SEMANTICSC
"SAPLV61Z" or "LV61ZU01"
"SEL_KONDTAB"
The termination occurred in the ABAP program "SAPLV61Z" in "SEL_KONDTAB".
The main program was "RM_MEPO_GUI ".
The termination occurred in line 537 of the source code of the (Include)
program "LV61ZU01"
of the source code of program "LV61ZU01" (when calling the editor 5370).
Processing was terminated because the exception "CX_SY_DYNAMIC_OSQL_SEMANTICS"
occurred in the
procedure "SEL_KONDTAB" "(FORM)" but was not handled locally, not declared in
the
RAISING clause of the procedure.
The procedure is in the program "SAPLV61Z ". Its source code starts in line 254
of the (Include) program "LV61ZU01 ".
005360 IF se_read_all_prestep IS INITIAL.
> SELECT * FROM (t681-kotab) APPENDING TABLE <cond_tab>
005380 UP TO 1 ROWS
005390 WHERE kappl = se_kappl
005400 AND kschl = se_kschl
005410 AND datbi >= se_date
005420 AND datab <= se_date
005430 AND (coding_tab).
005440 h_subrc = sy-subrc.
In the above statement execution its going for dump, when the (t681-kotab) value is A980 when i checked at debugging
Kindly help me out to solve the issue
Thanks in advance
Regards
KesavHi,
Do you have an integer field in the condition table A980? It looks like a field in the table is integer one and the system during creation of custom dynamic select statement adds as many spaces as possible before the integer value (integer values are right justified), so the statement exceeds the maximum length with an 'AND' or another condition clause.
Please check and provide more details if the issue is not resolved.
Regards,
Marcin -
Dump; while using LSMW with RFBIBL00.
Hi,
I am using Standard Batch/direct input method.
Ending up with a dump with the following error message:
The reason for the exception is:
The program attempted to interpret the value "/" as a number, but
since the value contravenes the rules for correct number formats,
this was not possible.
IF BBKPF-PROPMANO(1) NE NODATA.
CLEAR: FTPOST-FNAM, FTPOST-FVAL.
FTPOST-FNAM = 'BKPF-PROPMANO '.
FTPOST-FVAL = BBKPF-PROPMANO .
APPEND FTPOST.
ENDIF.
215 >>> IF BBKPF-VATDATE(1) NE NODATA.
CLEAR: FTPOST-FNAM, FTPOST-FVAL.
FTPOST-FNAM = 'BKPF-VATDATE '.
FTPOST-FVAL = BBKPF-VATDATE .
APPEND FTPOST.
ENDIF.
ENDFORM.
This code is a part of include program RFBIBL02.
While i am testing the same project in the sandbox system, it's working fine, as the condition
"IF BBKPF-VATDATE(1) NE NODATA"
is not there in the program RFBIBL02 (in sandbox system) .
Is there any way to bypass this condition or any other way to get it resolved?
Please suggest me a relevant solution.
Thanks.Hi ,
If u r not passing any value to the date field then no data value will be taken as '/'.
As date field cannot be given as '/' u r getting the dump.
Please clear the date field if there is no data. u can give the following piece of code in mapping section of that date field.
If not aritems-vatdate is initial.
bbkpf-vatdate = aritems-vatdate.
else.
clear bbkpf-vatdate.
endif.
this will clear the '/' value if there is no data in date field.
Reward points if useful.
Asif -
Hi,
I'm facing a problem using 2LIS_02_SCL: the field MCEKET-WAMNG is not populated during delta extraction (it is populated correctly when I fill setup tables).
I have been told that I should use customer exit EXIT_SAPLEINS_001 in order to fill MCEKET-WAMNG at event ML u2013 delivery, because 2LIS_02_SCL does not takes this event into account (only MA, MB, MC and MD which can be verified in LBWE Events), this field is not passed to BW in delta.
I need help to implement this solution.
An example with ABAP code will appreciated.
M.B.Hi,
May helpful to you
EXIT_SAPLRSAP_001 vs EXIT_SAPLEINS_001
EXIT_SAPLEINS_001
Regards,
Suman -
Short Dump while checking DataSource contents in R3 (Transaction RSA3)
Hello all,
I am having trouble with a DataSource (2LIS_11_VAITM) in the R3 Source System (IDES 6.0). When I try to view the contents of this DataSource through Transaction RSA3, I get the following Short Dump Error.....
Could someone pls help me with this.
Thanks,
SD
============================================================================
Runtime Errors CONNE_IMPORT_WRONG_STRUCTURE
Except. CX_SY_IMPORT_MISMATCH_ERROR
Date and Time 18.03.2009 09:56:23
Short text
Error when importing object "MC11VA0ITM_TAB".
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLMCEX" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_IMPORT_MISMATCH_ERROR', was
not caught in
procedure "MCEX_BW_LO_API" "(FUNCTION)", nor was it propagated by a RAISING
clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
When attempting to import data, the
structure of the complex object "MC11VA0ITM_TAB" was not compatible with the
target object. The error occurred with component no. 31.
Missing RAISING Clause in Interface
Program SAPLMCEX
Include LMCEXU06
Row 1
Module type (FUNCTION)
Module Name MCEX_BW_LO_API
Trigger Location of Exception
Program SAPLMCEX
Include LMCEXU06
Row 263
Module type (FUNCTION)
Module Name MCEX_BW_LO_APIHi SD,
The 11_Vaitm is a LO datasource, before checking its data setup tables need to be filled for it.
For filling the setup tables, first you have to delete the existing setup table data and ensure all the delta queues are empty.
Delete the setup tables: Go to TCODE LBWG and in the application give 11 and execute.
Delete all entries in Delta Queue, TCODE RSA7 for application 11.
Delete the entries in logistic queue: Check in TCODE SMQ1, if there are any entries for application .
Refill the setup tables: SBIW -> Settings for application specific datasources -> Logistics -> anaging extract strucutre -> Initilization -> Filling the setup table ->Application specific setup of data -> SD-Sales order perform setup.
Then try RSA3. Hope it helps.
Regards,
Pankaj -
Short dump while export grid alv with subtotals.
hello,
its strange and i face first time that my grid alv report goin to short dump while i done subtotals and send it to local file thru export.
if am not doing subtotals then export it to local file it goin fine.
whats it has problem plz give ur helping hends.
here i copied a dump msg also.
Short text
Error at assignment: Overwritten protected field.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLKKBL" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Error analysis
A new value is to be assigned to the field "<L_UNIT>", although this field is
entirely or partly protected against changes.
The following are protected against changes:
- Character literals or numeric literals
- Constants (CONSTANTS)
- Parameters of the category IMPORTING REFERENCE for functions and
methods
- Untyped field symbols not yet assigned a field using ASSIGN
- TABLES parameters if the actual parameter is protected against changes
- USING reference parameters and CHANGING parameters for FORMs, if the
actual parameter is protected against changes and
- Accesses using field symbols if the field assigned using ASSIGN is
protected (or partially protected, e.g. key components of an internal
table with the type SORTED or HASHED TABLE) against changes
- Accesses using references, if the field bound to the reference is
protected (or partially protected) against changes
- External write accesses to READ-ONLY attributes,
- Content of a shared object area instance accessed using a shared lock
(ATTACH_FOR_READ).
regards amit.& Object Id : &
& Object Name : &
& Function Module Name : Sales Register &
& Transaction Code : &
& Author : Amit gujargoud &
& Module Name : SD &
& Sub-Module : &
& Program Type : Dialog Create Date : 02/02/2007 &
& SAP Release : ECC 6.0 &
& Description : Sales Register - Detail &
*& Report ZSALESREGISTER
REPORT zsd_salesregister.
*& TYPE-POOLS
TYPE-POOLS : slis.
*& TABLES
TABLES: vbrp, "Billing Document: Item Data
vbrk, "Billing Document: Header Data
lips, "SD document: Delivery: Item data
lfa1, "Vendor Master (General Section)
kna1, "General Data in Customer Master
vbak, "Sales Document: Header Data
vbpa, "Sales Document: Partner (Gopal)
likp, "SD Document: Delivery Header Data
vbap, "Sales Document: Item Data
vbkd, "Sales Document: Business Data
mara. "General Material Data
*& DATA DECLARATION
DATA: BEGIN OF i_report OCCURS 100,
vbeln LIKE vbrp-vbeln, "Billing Document
posnr LIKE vbrp-posnr,
matnr LIKE mara-matnr ,
aubel LIKE vbrp-aubel, "Sales Document
fkimg LIKE vbrp-fkimg, "Actual billed quantity
vrkme LIKE vbrp-vrkme, "Sales unit
arktx LIKE vbrp-arktx, "Short text for sales order item
vgbel LIKE vbrp-vgbel, "Doc number of the reference document
werks LIKE vbap-werks,
vkgrp LIKE vbrp-vkgrp,
fklmg LIKE vbrp-fklmg,
volum LIKE vbrp-volum,
vkbur LIKE vbrp-vkbur,
vtweg_auft LIKE vbrp-vtweg_auft,
auart LIKE vbak-auart,
tabix LIKE sy-tabix, "Internal Table, Current Row Index
name1 LIKE kna1-name1, "Name1
exnum LIKE j_1iexchdr-exnum, "Official Excise Document Number
orqty TYPE p DECIMALS 0,
penqty TYPE p DECIMALS 0, "Cumulative order qty in sls units
openqty TYPE p DECIMALS 0, "Cumulative order qty in sls units
ean11 LIKE lips-ean11, "International Article No(EAN/UPC)
volum LIKE lips-volum,
lgmng LIKE lips-lgmng,
traid LIKE likp-traid,
ort01 LIKE lfa1-ort01, "City
lifnr LIKE lfa1-lifnr, "A/c Number of Vendor or Creditor
netwr LIKE vbrp-netwr, "Net val of bill item in doc currency
kunnr LIKE vbak-kunnr, "Sold-to party
adrnr LIKE vbpa-adrnr, "Address
city1 LIKE adrc-city1, "City
tprtr LIKE lfa1-name1, "Name 1
knumv LIKE konv-knumv, "Number of the document condition
kposn LIKE konv-kposn,
rate LIKE konv-kbetr, "Rate (cond amount or percentage)
bas_val LIKE konv-kwert, "Rate (cond amount or percentage)
exc_duty LIKE konv-kwert, "Rate (cond amount or percentage)
ed_cess LIKE konv-kwert, "Rate (cond amount or percentage)
freight LIKE konv-kwert, "Rate (cond amount or percentage)
pack LIKE konv-kwert, "Rate (cond amount or percentage)
cst LIKE konv-kwert, "Rate (cond amount or percentage)
vat LIKE konv-kwert, "Rate (cond amount or percentage)
ent_tax LIKE konv-kwert, "Rate (cond amount or percentage)
tot_inv LIKE konv-kwert, "Rate (cond amount or percentage)
tot_inv_round LIKE konv-kwert, "Rate (cond amount or percentage)
disc_tot LIKE konv-kwert, "Discount total - Z001 to Z020
vat_rate LIKE konv-kbetr,
cst_rate LIKE konv-kbetr,
lst_rate LIKE konv-kbetr,
mwsbk LIKE vbrk-mwsbk,
bas_tax LIKE konv-kwert,
dev_tax LIKE konv-kwert,
tcs_tax LIKE konv-kwert,
bas_tot LIKE konv-kwert,
lst LIKE konv-kwert,
vkorg LIKE vbak-vkorg,
mvgr1 LIKE mvke-mvgr1,
mvgr2 LIKE mvke-mvgr2,
mvgr3 LIKE mvke-mvgr3,
mvgr4 LIKE mvke-mvgr4,
mvgr5 LIKE mvke-mvgr5,
text1 LIKE tvm1t-bezei,
text2 LIKE tvm1t-bezei,
text3 LIKE tvm1t-bezei,
text4 LIKE tvm1t-bezei,
text5 LIKE tvm1t-bezei,
bismit_area TYPE p DECIMALS 4, " Size (L*B) in mm
face_area TYPE p DECIMALS 2, " Face Area Declaration
notional_area TYPE p DECIMALS 2,
stock_pcs TYPE p , " decimals 3 Pcs of Stock
labst LIKE mard-labst, " Valuated Unrestricted-Use Stock
bismt LIKE mara-bismt, " Size (L*B) in mm
normt LIKE mara-normt, " Industry Standard Description
temp TYPE p DECIMALS 2,
temp1 TYPE p DECIMALS 2,
temp2 TYPE p DECIMALS 2,
temp3 TYPE p DECIMALS 2,
temp4 TYPE p DECIMALS 2,
temp5 TYPE p DECIMALS 2,
temp6 TYPE p DECIMALS 2,
temp7 TYPE p DECIMALS 2,
temp8 TYPE p DECIMALS 2,
temp9 TYPE p DECIMALS 2,
temp10 TYPE p DECIMALS 2,
temp11 TYPE p DECIMALS 2,
temp12 TYPE p DECIMALS 2,
temp13 TYPE p DECIMALS 0,
temp14 TYPE p DECIMALS 0,
temp15 TYPE p DECIMALS 0,
temp16 TYPE p DECIMALS 2,
temp17 TYPE p DECIMALS 2,
temp18 TYPE p DECIMALS 2,
temp19 TYPE p DECIMALS 2,
temp20 TYPE p DECIMALS 2,
temp21 TYPE p DECIMALS 2,
waybill(20) TYPE c,
audat LIKE vbak-audat, "Document Date (Date Received/Sent)
lgort LIKE vbap-lgort, "Storage location
lgobe LIKE t001l-lgobe, "Description of storage location
erdat LIKE vbrk-erdat, "Date on which the record was created
exdat LIKE j_1iexchdr-exdat, "Excise Document Date
vbtyp LIKE vbak-vbtyp, "SD document category
acdt LIKE likp-wadat_ist, "Actual goods movement date
fkdat LIKE vbrk-fkdat,
ship LIKE kna1-name1, "Name1 (Ship-to party)
fksto LIKE vbrk-fksto,
fkart LIKE vbrk-fkart,
bezei LIKE t005u-bezei,
vtweg LIKE vbak-vtweg,
spart LIKE vbak-spart,
matkl LIKE mara-matkl,
wgbez LIKE t023t-wgbez,
mtart LIKE mara-mtart,
labor LIKE mara-labor,
ferth LIKE mara-ferth,
lbtxt LIKE t024x-lbtxt,
niels LIKE kna1-niels,
kukla LIKE kna1-kukla,
desc LIKE tvkbt-bezei,
brsch LIKE kna1-brsch,
zeinr LIKE mara-zeinr,
bzirk LIKE vbrk-bzirk,
area_desc LIKE tnlst-bezei,
dist_desc TYPE tkukt-vtext,
taluka_desc TYPE t016t-brtxt,
sales_desc TYPE tvgrt-bezei,
kmein LIKE konv-kmein, "Sales Unit
challan LIKE likp-vbeln,
END OF i_report.
data for MVKE
DATA: BEGIN OF i_report_mvke OCCURS 0,
vbeln LIKE vbrp-vbeln, "Billing Document
aubel LIKE vbrp-aubel, "Sales Document
vkorg LIKE vbak-vkorg,
matnr LIKE mara-matnr ,
vtweg LIKE vbak-vtweg,
END OF i_report_mvke.
***********************TEMP COPY
DATA: BEGIN OF i_report_temp OCCURS 0,
vbeln LIKE vbrp-vbeln, "Billing Document
posnr LIKE vbrp-posnr,
matnr LIKE mara-matnr ,
aubel LIKE vbrp-aubel, "Sales Document
fkimg LIKE vbrp-fkimg, "Actual billed quantity
vrkme LIKE vbrp-vrkme, "Sales unit
arktx LIKE vbrp-arktx, "Short text for sales order item
vgbel LIKE vbrp-vgbel, "Doc number of the reference document
werks LIKE vbap-werks,
vkgrp LIKE vbrp-vkgrp,
fklmg LIKE vbrp-fklmg,
volum LIKE vbrp-volum,
vkbur LIKE vbrp-vkbur,
vtweg_auft LIKE vbrp-vtweg_auft,
auart LIKE vbak-auart,
tabix LIKE sy-tabix, "Internal Table, Current Row Index
name1 LIKE kna1-name1, "Name1
exnum LIKE j_1iexchdr-exnum, "Official Excise Document Number
orqty TYPE p DECIMALS 0,
penqty TYPE p DECIMALS 0, "Cumulative order qty in sls units
openqty TYPE p DECIMALS 0, "Cumulative order qty in sls units
ean11 LIKE lips-ean11, "International Article No(EAN/UPC)
volum LIKE lips-volum,
lgmng LIKE lips-lgmng,
traid LIKE likp-traid,
ort01 LIKE lfa1-ort01, "City
lifnr LIKE lfa1-lifnr, "A/c Number of Vendor or Creditor
netwr LIKE vbrp-netwr, "Net val of bill item in doc currency
kunnr LIKE vbak-kunnr, "Sold-to party
adrnr LIKE vbpa-adrnr, "Address
city1 LIKE adrc-city1, "City
tprtr LIKE lfa1-name1, "Name 1
knumv LIKE konv-knumv, "Number of the document condition
kposn LIKE konv-kposn,
rate LIKE konv-kbetr, "Rate (cond amount or percentage)
bas_val LIKE konv-kwert, "Rate (cond amount or percentage)
exc_duty LIKE konv-kwert, "Rate (cond amount or percentage)
ed_cess LIKE konv-kwert, "Rate (cond amount or percentage)
freight LIKE konv-kwert, "Rate (cond amount or percentage)
pack LIKE konv-kwert, "Rate (cond amount or percentage)
cst LIKE konv-kwert, "Rate (cond amount or percentage)
vat LIKE konv-kwert, "Rate (cond amount or percentage)
ent_tax LIKE konv-kwert, "Rate (cond amount or percentage)
tot_inv LIKE konv-kwert, "Rate (cond amount or percentage)
tot_inv_round LIKE konv-kwert, "Rate (cond amount or percentage)
disc_tot LIKE konv-kwert, "Discount total - Z001 to Z020
vat_rate LIKE konv-kbetr,
cst_rate LIKE konv-kbetr,
lst_rate LIKE konv-kbetr,
mwsbk LIKE vbrk-mwsbk,
bas_tax LIKE konv-kwert,
dev_tax LIKE konv-kwert,
tcs_tax LIKE konv-kwert,
bas_tot LIKE konv-kwert,
lst LIKE konv-kwert,
vkorg LIKE vbak-vkorg,
mvgr1 LIKE mvke-mvgr1,
mvgr2 LIKE mvke-mvgr2,
mvgr3 LIKE mvke-mvgr3,
mvgr4 LIKE mvke-mvgr4,
mvgr5 LIKE mvke-mvgr5,
text1 LIKE tvm1t-bezei,
text2 LIKE tvm1t-bezei,
text3 LIKE tvm1t-bezei,
text4 LIKE tvm1t-bezei,
text5 LIKE tvm1t-bezei,
bismit_area TYPE p DECIMALS 4, " Size (L*B) in mm
face_area TYPE p DECIMALS 2, " Face Area Declaration
notional_area TYPE p DECIMALS 2,
stock_pcs TYPE p , " decimals 3 Pcs of Stock
labst LIKE mard-labst, " Valuated Unrestricted-Use Stock
bismt LIKE mara-bismt, " Size (L*B) in mm
normt LIKE mara-normt, " Industry Standard Description
temp TYPE p DECIMALS 2,
temp1 TYPE p DECIMALS 2,
temp2 TYPE p DECIMALS 2,
temp3 TYPE p DECIMALS 2,
temp4 TYPE p DECIMALS 2,
temp5 TYPE p DECIMALS 2,
temp6 TYPE p DECIMALS 2,
temp7 TYPE p DECIMALS 2,
temp8 TYPE p DECIMALS 2,
temp9 TYPE p DECIMALS 2,
temp10 TYPE p DECIMALS 2,
temp11 TYPE p DECIMALS 2,
temp12 TYPE p DECIMALS 2,
temp13 TYPE p DECIMALS 0,
temp14 TYPE p DECIMALS 0,
temp15 TYPE p DECIMALS 0,
temp16 TYPE p DECIMALS 2,
temp17 TYPE p DECIMALS 2,
temp18 TYPE p DECIMALS 2,
temp19 TYPE p DECIMALS 2,
temp20 TYPE p DECIMALS 2,
temp21 TYPE p DECIMALS 2,
waybill(20) TYPE c,
audat LIKE vbak-audat, "Document Date (Date Received/Sent)
lgort LIKE vbap-lgort, "Storage location
lgobe LIKE t001l-lgobe, "Description of storage location
erdat LIKE vbrk-erdat, "Date on which the record was created
exdat LIKE j_1iexchdr-exdat, "Excise Document Date
vbtyp LIKE vbak-vbtyp, "SD document category
acdt LIKE likp-wadat_ist, "Actual goods movement date
fkdat LIKE vbrk-fkdat,
ship LIKE kna1-name1, "Name1 (Ship-to party)
fksto LIKE vbrk-fksto,
fkart LIKE vbrk-fkart,
bezei LIKE t005u-bezei,
vtweg LIKE vbak-vtweg,
spart LIKE vbak-spart,
matkl LIKE mara-matkl,
wgbez LIKE t023t-wgbez,
mtart LIKE mara-mtart,
labor LIKE mara-labor,
ferth LIKE mara-ferth,
lbtxt LIKE t024x-lbtxt,
niels LIKE kna1-niels,
kukla LIKE kna1-kukla,
desc LIKE tvkbt-bezei,
brsch LIKE kna1-brsch,
zeinr LIKE mara-zeinr,
bzirk LIKE vbrk-bzirk,
area_desc LIKE tnlst-bezei,
dist_desc TYPE tkukt-vtext,
taluka_desc TYPE t016t-brtxt,
sales_desc TYPE tvgrt-bezei,
kmein LIKE konv-kmein, "Sales Unit
challan LIKE likp-vbeln,
END OF i_report_temp.
DATA: BEGIN OF i_vbap OCCURS 0 ,
posnr LIKE vbap-posnr,
vbeln LIKE vbap-vbeln ,
matnr LIKE vbap-matnr ,
werks LIKE vbap-werks,
kwmeng LIKE vbap-kwmeng,
lgort LIKE vbap-lgort,
matkl LIKE mara-matkl,
wgbez LIKE t023t-wgbez,
mtart LIKE mara-mtart,
END OF i_vbap .
DATA : w_temp_cal(20) TYPE c.
DATA : w_face_area TYPE p DECIMALS 4,
w_notinal_area TYPE p DECIMALS 4.
**MVKE
DATA: BEGIN OF itab_mvke OCCURS 0,
matnr LIKE mvke-matnr,
vkorg LIKE vbak-vkorg,
vtweg LIKE mvke-vtweg,
mvgr1 LIKE mvke-mvgr1,
mvgr2 LIKE mvke-mvgr2,
mvgr3 LIKE mvke-mvgr3,
mvgr4 LIKE mvke-mvgr4,
mvgr5 LIKE mvke-mvgr5,
END OF itab_mvke.
**TVM1T
DATA : BEGIN OF itab_tvm1t OCCURS 0,
spras LIKE tvm1t-spras,
mvgr1 LIKE tvm1t-mvgr1,
bezei LIKE tvm1t-bezei,
END OF itab_tvm1t.
DATA : BEGIN OF itab_tvm2t OCCURS 0,
spras LIKE tvm2t-spras,
mvgr2 LIKE tvm2t-mvgr2,
bezei LIKE tvm2t-bezei,
END OF itab_tvm2t.
DATA : BEGIN OF itab_tvm3t OCCURS 0,
spras LIKE tvm3t-spras,
mvgr3 LIKE tvm3t-mvgr3,
bezei LIKE tvm3t-bezei,
END OF itab_tvm3t.
DATA : BEGIN OF itab_tvm4t OCCURS 0,
spras LIKE tvm4t-spras,
mvgr4 LIKE tvm4t-mvgr4,
bezei LIKE tvm4t-bezei,
END OF itab_tvm4t.
DATA : BEGIN OF itab_tvm5t OCCURS 0,
spras LIKE tvm5t-spras,
mvgr5 LIKE tvm5t-mvgr5,
bezei LIKE tvm5t-bezei,
END OF itab_tvm5t.
DATA: itab_t024x TYPE STANDARD TABLE OF t024x WITH HEADER LINE,
it_report LIKE LINE OF i_report OCCURS 0,
i_mvke LIKE LINE OF itab_mvke OCCURS 0.
**VBKD
DATA: BEGIN OF i_vbkd OCCURS 0 ,
vbeln LIKE vbkd-vbeln ,
posnr LIKE vbkd-posnr ,
bzirk LIKE vbkd-bzirk ,
END OF i_vbkd .
DATA: BEGIN OF i_lips OCCURS 0,
vbeln LIKE lips-vbeln,
ean11 LIKE lips-ean11,
volum LIKE lips-volum,
lgmng LIKE lips-lgmng,
waybill(20) TYPE c,
END OF i_lips.
DATA: BEGIN OF i_vbrk OCCURS 0,
vbeln LIKE vbrk-vbeln,
rfbsk LIKE vbrk-rfbsk, "Status for transfer to accounting
erdat LIKE vbrk-erdat, "Dt on which the record was created
fkdat LIKE vbrk-fkdat, "CHANGE MADE BY PARTHA RAHAMAN
fksto LIKE vbrk-fksto, "GOPAL:: CANCELLED DOC. DO NOT PRNT.
netwr LIKE vbrk-netwr,
fkart LIKE vbrk-fkart, "Gopal:when billng typ=s1 do not pnt 1jul
knumv LIKE vbrk-knumv,
mwsbk LIKE vbrk-mwsbk,
bzirk LIKE vbrk-bzirk,
vtweg LIKE vbrk-vtweg,
spart LIKE vbrk-spart,
END OF i_vbrk.
*structure for MARD Table by kalika
DATA : BEGIN OF itab_mard OCCURS 0,
matnr LIKE mard-matnr,
werks LIKE mard-werks,
labst LIKE mard-labst, " Valuated Unrestricted-Use Stock
lgort LIKE mard-lgort, " Storage Location
END OF itab_mard.
*structure for MARD Table by kalika
DATA:BEGIN OF i_kna1 OCCURS 0,
vbeln LIKE vbak-vbeln,
name1 LIKE kna1-name1,
kunnr LIKE kna1-kunnr,
regio LIKE kna1-regio,
bezei LIKE t005u-bezei,
land1 LIKE kna1-land1,
vkgrp LIKE vbak-vkgrp,
niels LIKE kna1-niels,
kukla LIKE kna1-kukla,
brsch LIKE kna1-brsch,
vkbur LIKE vbak-vkbur,
END OF i_kna1.
DATA:BEGIN OF i_t005u OCCURS 0,
spras LIKE t005u-spras,
land1 LIKE t005u-land1,
bland LIKE t005u-bland,
bezei LIKE t005u-bezei,
END OF i_t005u.
DATA:BEGIN OF i_tnlst OCCURS 0,
spras LIKE t005u-spras,
niels LIKE tnlst-niels,
bezei LIKE t005u-bezei,
END OF i_tnlst.
DATA:BEGIN OF itab_tkukt OCCURS 0,
spras LIKE tkukt-spras,
kukla LIKE tkukt-kukla,
vtext LIKE tkukt-vtext,
END OF itab_tkukt.
DATA : BEGIN OF itab_t016t OCCURS 0,
spras LIKE t016t-spras,
brsch LIKE t016t-brsch,
brtxt LIKE t016t-brtxt,
END OF itab_t016t.
DATA : BEGIN OF itab_tvgrt OCCURS 0,
spras LIKE tvgrt-spras,
vkgrp LIKE tvgrt-vkgrp,
bezei LIKE tvgrt-bezei,
END OF itab_tvgrt.
*DATA: i_t005u TYPE STANDARD TABLE OF t005u WITH HEADER LINE.
DATA:BEGIN OF i_kna2 OCCURS 0,
kunnr LIKE kna1-kunnr,
name1 LIKE kna1-name1, " For Ship-to-Party
END OF i_kna2.
DATA:BEGIN OF i_vbak OCCURS 0,
vbeln LIKE vbak-vbeln,
vbtyp LIKE vbak-vbtyp,
audat LIKE vbak-audat,
auart LIKE vbak-auart,
vtweg LIKE vbak-vtweg,
spart LIKE vbak-spart,
vkbur LIKE vbak-vkbur,
vkorg LIKE vbak-vkorg,
END OF i_vbak.
DATA:BEGIN OF i_adrc OCCURS 0,
vbeln LIKE vbpa-vbeln,
kunnr LIKE kna1-kunnr,
city1 LIKE adrc-city1,
name1 LIKE kna1-name1, "Name1 (Ship-to party)
END OF i_adrc.
DATA:BEGIN OF i_lfa1 OCCURS 0,
lifnr LIKE vbpa-lifnr,
vbeln LIKE vbpa-vbeln,
name1 LIKE lfa1-name1,
END OF i_lfa1.
DATA : BEGIN OF it_knumv OCCURS 0,
vbeln LIKE vbrk-vbeln,
knumv LIKE vbrk-knumv,
END OF it_knumv.
DATA : BEGIN OF it_rate OCCURS 0,
ksteu LIKE konv-ksteu, "Condition control
knumv LIKE konv-knumv, "Number of the document condition
kschl LIKE konv-kschl, "Condition type
kbetr LIKE konv-kbetr, "Rate (condition amount or percentage)
kwert LIKE konv-kwert, "Condition value
kposn LIKE konv-kposn,
kmein LIKE konv-kmein, "Sales Unit
END OF it_rate.
DATA: BEGIN OF itab_exnum OCCURS 0,
exnum LIKE j_1iexchdr-exnum, "Official Excise Document Number
exdat LIKE j_1iexchdr-exdat, "Excise Document Date
rdoc LIKE j_1iexchdr-rdoc, "Reference Document 1
status LIKE j_1iexchdr-status,
END OF itab_exnum.
DATA: BEGIN OF itab_qty OCCURS 0,
kwmeng LIKE vbap-kwmeng,
vbeln LIKE vbap-vbeln,
lgort LIKE vbap-lgort,
END OF itab_qty.
*DATA: BEGIN OF i_stloc OCCURS 0,
lgort LIKE t001l-lgort,
lgobe LIKE t001l-lgobe,
END OF i_stloc.
DATA:t_line LIKE STANDARD TABLE OF tline INITIAL SIZE 0
WITH HEADER LINE,
" itab_tvkbt LIKE STANDARD TABLE OF tvkbt WITH HEADER LINE,
w_tdname LIKE thead-tdname.
DATA : BEGIN OF itab_tvkbt OCCURS 0,
spras LIKE tvkbt-spras,
vkbur LIKE tvkbt-vkbur,
bezei LIKE tvkbt-bezei,
END OF itab_tvkbt.
DATA: BEGIN OF i_exchdr OCCURS 0,
exnum LIKE j_1iexchdr-exnum,
exdat LIKE j_1iexchdr-exdat,
rdoc LIKE j_1iexchdr-rdoc,
END OF i_exchdr.
DATA: BEGIN OF i_likp OCCURS 0,
vbeln LIKE likp-vbeln,
wadat_ist LIKE likp-wadat_ist,
traid LIKE likp-traid,
bolnr LIKE likp-bolnr,
END OF i_likp.
DATA: BEGIN OF i_mara OCCURS 0,
matnr LIKE mara-matnr,
matkl LIKE mara-matkl,
mtart LIKE mara-mtart,
labor LIKE mara-labor,
wgbez LIKE t023t-wgbez,
bismt LIKE mara-bismt,
normt LIKE mara-normt,
ferth LIKE mara-ferth,
zeinr LIKE mara-zeinr,
extwg LIKE mara-extwg,
spart LIKE mara-spart,
END OF i_mara.
DATA: BEGIN OF i_t023t OCCURS 0,
matkl LIKE t023t-matkl,
wgbez LIKE t023t-wgbez,
END OF i_t023t.
DATA : var_length(20) TYPE c,
var_breadth(20) TYPE c.
DATA: p_w_value LIKE konv-kwert.
DATA : it_fieldcat TYPE slis_t_fieldcat_alv, " Event for Table to creater fieldcatalog
wa_fieldcat LIKE LINE OF it_fieldcat, " Work Area for table field catalog
lt_top_of_page TYPE slis_t_listheader, " Header table for top of page
i_layout TYPE slis_layout_alv . " It will fill the layout
gt_event TYPE slis_t_event. " Table Event
*DATA :
"itab_tnlst TYPE STANDARD TABLE OF tnlst WITH HEADER LINE,
" itab_tkukt TYPE STANDARD TABLE OF tkukt WITH HEADER LINE,
*" itab_t016t TYPE STANDARD TABLE OF t016t WITH HEADER LINE,
itab_tvgrt TYPE STANDARD TABLE OF tvgrt WITH HEADER LINE.
*& SELECTION-SCREEN
SELECTION-SCREEN BEGIN OF BLOCK block
WITH FRAME TITLE text-100.
SELECT-OPTIONS: s_date FOR vbrk-fkdat OBLIGATORY,
s_vkbur FOR vbak-vkbur OBLIGATORY,
s_vtweg FOR vbrk-vtweg OBLIGATORY,
s_werks FOR vbap-werks,
s_spart FOR vbrk-spart OBLIGATORY,
s_matkl FOR mara-matkl.
PARAMETERS:
r_opt3 RADIOBUTTON GROUP grp1,
r_opt2 RADIOBUTTON GROUP grp1.
r_opt4 RADIOBUTTON GROUP grp1,
r_opt5 RADIOBUTTON GROUP grp1,
r_opt1 RADIOBUTTON GROUP grp1.
SELECTION-SCREEN END OF BLOCK block.
*& INITIALIZATION
INITIALIZATION.
r_opt2 = 'X'.
*& START-OF-SELECTION.
START-OF-SELECTION.
*select data from VBRP
SELECT vbeln
posnr
matnr
aubel
fkimg
vrkme
arktx
vgbel
werks
vkgrp
fklmg
volum
vkbur
vtweg_auft
FROM vbrp
INTO TABLE i_report
WHERE "erdat IN s_date
AND spart IN s_spart
vkbur IN s_vkbur
AND vtweg_auft IN s_vtweg.
**logic for Pending, Summary & Detail Report
IF
r_opt1 EQ 'X' OR
r_opt2 EQ 'X' OR
r_opt3 EQ 'X'.
SELECT vbeln
rfbsk
erdat
fkdat
fksto
netwr
fkart
knumv
mwsbk
bzirk
vtweg
spart
FROM vbrk INTO TABLE i_vbrk
FOR ALL ENTRIES IN i_report
WHERE "vbeln = i_report-vbeln
" and
fkdat IN s_date
AND fkart IN ('ZBHR', 'ZTZT', 'ZKRP', 'ZRUD', 'ZBSR',
'ZGHT', 'ZKOL', 'ZPTN', 'ZRNC', 'ZCND',
'ZDLH', 'ZGZB', 'ZGUR', 'ZHSR', 'ZJPR',
'ZLKW', 'ZBLR', 'ZCHN', 'ZCBM', 'ZHUB',
'ZHYD', 'ZKOC', 'ZAHD', 'ZIND', 'ZMUM',
*********************MODIFICATION BY CHAKRAPANI (ADDITION OF ZVIJ AND ZHWH ) 18.05.2007
'ZNGP', 'ZPNE', 'ZRPR' , 'ZEXP', 'ZDEM','ZVIJ', 'ZHWH','JEX' )
*********************MODIFICATION BY CHAKRAPANI (ADDITION OF ZVIJ AND ZHWH ) 18.05.2007
AND vtweg IN s_vtweg
AND spart IN s_spart
AND fksto NE 'X'.
IF i_vbrk[] IS NOT INITIAL.
SELECT vbeln
posnr
matnr
aubel
fkimg
vrkme
arktx
vgbel
werks
vkgrp
fklmg
volum
vkbur
vtweg_auft
FROM vbrp
INTO TABLE i_report
FOR ALL ENTRIES IN i_vbrk
WHERE vbeln = i_vbrk-vbeln "erdat IN s_date
AND spart IN s_spart
AND vkbur IN s_vkbur
AND vtweg_auft IN s_vtweg.
ENDIF.
ELSEIF r_opt4 EQ 'X' OR
r_opt5 EQ 'X'.
SELECT vbeln
rfbsk
erdat
fkdat
fksto
netwr
fkart
knumv
mwsbk
bzirk
vtweg
spart
FROM vbrk INTO CORRESPONDING FIELDS OF TABLE i_vbrk
FROM vbrk INTO TABLE i_vbrk
FOR ALL ENTRIES IN i_report
WHERE vbeln = i_report-vbeln
AND fkart EQ 'ZEXP'
AND vtweg IN s_vtweg
AND spart IN s_spart
AND fksto NE 'X'.
ENDIF.
SORT i_vbrk BY vbeln ASCENDING.
ENDIF.
change amit by my self may be removed
IF i_report[] IS NOT INITIAL.
REFRESH it_report.
it_report[] = i_report[].
DELETE ADJACENT DUPLICATES FROM it_report COMPARING aubel.
SORT it_report BY aubel.
*select VBAP data
SELECT posnr vbeln matnr werks
kwmeng lgort
FROM vbap
INTO TABLE i_vbap
FOR ALL ENTRIES IN it_report
WHERE vbeln = it_report-aubel.
ENDIF.
change amit by my self may be removed
*select data from VBKD
IF NOT i_vbap[] IS INITIAL.
SELECT vbeln posnr
FROM vbkd
INTO TABLE i_vbkd
FOR ALL ENTRIES IN i_vbap
WHERE vbeln = i_vbap-vbeln.
ENDIF.
SORT i_vbap BY vbeln ASCENDING.
IF i_report[] IS NOT INITIAL.
REFRESH it_report.
it_report[] = i_report[].
DELETE ADJACENT DUPLICATES FROM it_report COMPARING matnr.
SORT it_report BY matnr.
SELECT
matnr
matkl
mtart
labor
bismt
normt
ferth
zeinr
extwg
spart
FROM mara
INTO TABLE i_mara
FOR ALL ENTRIES IN i_report
WHERE matnr = i_report-matnr
AND spart IN s_spart.
ENDIF.
IF NOT i_mara[] IS INITIAL.
SORT i_mara BY matnr.
SELECT matnr
labst
FROM mard
INTO TABLE itab_mard
FOR ALL ENTRIES IN i_mara
WHERE matnr = i_mara-matnr.
ENDIF.
ENDIF.
DATA : it_mara LIKE LINE OF i_mara OCCURS 0.
IF NOT i_mara[] IS INITIAL.
REFRESH it_mara.
it_mara[] = i_mara[].
DELETE ADJACENT DUPLICATES FROM it_mara COMPARING matkl.
SORT it_mara BY matkl.
SELECT matkl wgbez
FROM t023t
INTO TABLE i_t023t
FOR ALL ENTRIES IN it_mara
WHERE matkl = it_mara-matkl.
*T024X
REFRESH it_mara.
it_mara[] = i_mara[].
DELETE ADJACENT DUPLICATES FROM it_mara COMPARING labor.
SORT it_mara BY labor.
SELECT * FROM t024x
INTO TABLE itab_t024x
FOR ALL ENTRIES IN it_mara
WHERE labor = it_mara-labor
AND spras = sy-langu.
ENDIF.
*begin of change amit
LOOP AT i_vbap.
READ TABLE i_mara WITH KEY matnr = i_vbap-matnr.
IF sy-subrc = 0.
*material type & material group
i_vbap-mtart = i_mara-mtart.
i_vbap-matkl = i_mara-matkl.
ENDIF.
MODIFY i_vbap.
ENDLOOP.
*Material Group Description
*end of change amit
IF i_report[] IS NOT INITIAL.
REFRESH it_report.
it_report[] = i_report[].
DELETE ADJACENT DUPLICATES FROM it_report COMPARING vgbel.
SORT it_report BY vgbel.
SELECT vbeln
ean11
volum
lgmng
FROM lips
INTO TABLE i_lips
FOR ALL ENTRIES IN it_report
WHERE vbeln = it_report-vgbel.
ENDIF.
IF i_report[] IS NOT INITIAL.
REFRESH it_report.
it_report[] = i_report[].
SORT it_report BY vgbel.
DELETE ADJACENT DUPLICATES FROM it_report COMPARING vgbel.
IF i_lips[] IS NOT INITIAL.
SELECT vbeln
wadat_ist
traid
bolnr
FROM likp
INTO TABLE i_likp
FOR ALL ENTRIES IN it_report
WHERE vbeln = it_report-vgbel.
ENDIF.
SORT i_lips BY vbeln ASCENDING.
LOOP AT i_lips.
REFRESH t_line.
CLEAR w_tdname.
w_tdname = i_lips-vbeln.
CALL FUNCTION 'READ_TEXT'
EXPORTING
client = sy-mandt
id = 'ZVOW'
language = sy-langu
name = w_tdname
object = 'VBBK'
TABLES
lines = t_line
EXCEPTIONS
id = 1
language = 2
name = 3
not_found = 4
object = 5
reference_check = 6
wrong_access_to_archive = 7
OTHERS = 8.
IF sy-subrc <> 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
LOOP AT t_line.
CONCATENATE i_lips-waybill t_line-tdline INTO i_lips-waybill.
ENDLOOP.
IF sy-subrc EQ 0.
MODIFY i_lips.
ENDIF.
ENDLOOP.
*IF i_report[] IS NOT INITIAL.
REFRESH it_report.
it_report[] = i_report[].
SORT it_report BY aubel.
DELETE ADJACENT DUPLICATES FROM it_report COMPARING aubel.
SELECT a~vbeln
b~name1
b~kunnr
b~regio
b~land1
a~vkgrp
b~niels
b~kukla
b~brsch
a~vkbur
FROM vbak AS a
INNER JOIN kna1 AS b
ON akunnr = bkunnr
INTO TABLE i_kna1
FOR ALL ENTRIES IN i_report
WHERE vbeln = i_report-aubel.
AND land1 = 'IN'.
*endif.
DATA : it_kna1 LIKE LINE OF i_kna1 OCCURS 0.
IF NOT i_kna1[] IS INITIAL.
REFRESH it_kna1.
it_kna1[] = i_kna1[].
SORT it_kna1 BY regio.
DELETE ADJACENT DUPLICATES FROM it_kna1 COMPARING regio.
SELECT spras
land1
bland
bezei FROM t005u
INTO TABLE i_t005u
FOR ALL ENTRIES IN it_kna1
WHERE bland = it_kna1-regio
AND spras = 'EN' AND land1 = 'IN'.
REFRESH it_kna1.
it_kna1[] = i_kna1[].
SORT it_kna1 BY niels.
DELETE ADJACENT DUPLICATES FROM it_kna1 COMPARING niels.
SELECT spras niels bezei FROM tnlst
INTO TABLE i_tnlst
FOR ALL ENTRIES IN it_kna1
WHERE niels = it_kna1-niels
AND spras = sy-langu.
REFRESH it_kna1.
it_kna1[] = i_kna1[].
SORT it_kna1 BY kukla.
DELETE ADJACENT DUPLICATES FROM it_kna1 COMPARING kukla.
SELECT spras kukla vtext FROM tkukt
INTO TABLE itab_tkukt
FOR ALL ENTRIES IN it_kna1
WHERE kukla = it_kna1-kukla
AND spras = sy-langu.
REFRESH it_kna1.
it_kna1[] = i_kna1[].
SORT it_kna1 BY brsch.
DELETE ADJACENT DUPLICATES FROM it_kna1 COMPARING brsch.
SELECT spras brsch brtxt FROM t016t
INTO TABLE itab_t016t
FOR ALL ENTRIES IN it_kna1
WHERE brsch = it_kna1-brsch
AND spras = sy-langu.
REFRESH it_kna1.
it_kna1[] = i_kna1[].
SORT it_kna1 BY vkgrp.
DELETE ADJACENT DUPLICATES FROM it_kna1 COMPARING vkgrp.
SELECT spras vkgrp bezei FROM tvgrt
INTO TABLE itab_tvgrt
FOR ALL ENTRIES IN it_kna1
WHERE vkgrp = it_kna1-vkgrp
AND spras = sy-langu.
ENDIF.
SORT i_kna1 BY vbeln ASCENDING.
IF i_report[] IS NOT INITIAL.
REFRESH it_report.
it_report[] = i_report[].
SORT it_report BY aubel.
DELETE ADJACENT DUPLICATES FROM it_report COMPARING aubel.
SELECT a~vbeln
a~kunnr
b~city1
FROM vbpa AS a
INNER JOIN adrc AS b
ON aadrnr = baddrnumber
INTO TABLE i_adrc
FOR ALL ENTRIES IN it_report
WHERE vbeln = it_report-aubel
AND parvw = 'WE'.
SORT i_adrc BY vbeln ASCENDING.
ENDIF.
DATA : it_adrc LIKE LINE OF i_adrc OCCURS 0.
IF i_adrc[] IS NOT INITIAL.
REFRESH it_adrc.
it_adrc[] = i_adrc[].
SORT it_adrc BY kunnr.
DELETE ADJACENT DUPLICATES FROM it_adrc COMPARING kunnr.
SELECT kunnr name1
FROM kna1
INTO TABLE i_kna2
FOR ALL ENTRIES IN it_adrc
WHERE kunnr = it_adrc-kunnr.
ENDIF.
SELECT a~lifnr
a~vbeln
b~name1
FROM vbpa AS a
INNER JOIN lfa1 AS b
ON alifnr = blifnr
INTO TABLE i_lfa1
FOR ALL ENTRIES IN i_report
WHERE vbeln = i_report-vgbel
AND parvw = 'SP'.
SORT i_lfa1 BY vbeln ASCENDING.
change amit by my self may be removed
IF i_report[] IS NOT INITIAL.
REFRESH it_report.
it_report[] = i_report[].
SORT it_report BY vbeln.
DELETE ADJACENT DUPLICATES FROM it_report COMPARING vbeln.
SELECT exnum
exdat
rdoc
status
FROM j_1iexchdr
INTO TABLE itab_exnum
FOR ALL ENTRIES IN it_report
WHERE rdoc = it_report-vbeln AND status = 'P' OR status = 'C' .
ENDIF.
change amit by my self may be removed
change amit by my self may be removed
IF i_report[] IS NOT INITIAL.
REFRESH it_report.
it_report[] = i_report[].
SORT it_report BY aubel.
DELETE ADJACENT DUPLICATES FROM it_report COMPARING aubel.
SELECT kwmeng
vbeln
lgort
FROM vbap
INTO TABLE itab_qty
FOR ALL ENTRIES IN it_report
WHERE vbeln = it_report-aubel.
ENDIF.
change amit by my self may be removed
SORT itab_qty BY vbeln.
CHECK NOT i_vbrk[] IS INITIAL.
SORT i_report BY vbeln.
DATA : t_vbrk LIKE LINE OF i_vbrk OCCURS 0.
REFRESH t_vbrk.
t_vbrk[] = i_vbrk[].
SORT t_vbrk BY knumv.
DELETE ADJACENT DUPLICATES FROM t_vbrk COMPARING knumv.
SELECT ksteu
knumv
kschl
kbetr
kwert
kposn
kmein
FROM konv
INTO TABLE it_rate
FOR ALL ENTRIES IN t_vbrk
WHERE knumv = t_vbrk-knumv
AND kschl IN ('ZR00', "Basic Price
'ZR01', "Basic Price
'ZR02', "Basic Price
'ZR03', "Basic Price
'ZR04', "Basic Price
'ZR05', "Basic Price
'JEXP', "Excise
'JECS', "ED
'ZG03', "Freight
'ZG04', "Freight
'JCST', "CST
'JLST', "LST
'ZDEV', "Dev Tax
'Z001', "Discount
'Z002', "Discount
'Z003', "Discount
'Z004', "Discount
'Z005', "Discount
'Z006', "Discount
'Z007', "Discount -
Error with Dump while adding Currency field in UI
Hello,
I have a requirement to add a custom entity in MDGM with an currency attribute, and encountring dump while adding the field to Web Dynpro component in UI.
Could some one point me a direction and see below :
Custom Entity with attributes
ZTSTOCK data element is type curr (Lenght 13, Dec 2)
Data Model is activated without errors and created custom Web Dynpro Form component. while designing it in UIBB by adding Element TSTOCK_VL encountring a error and dump.
Error: Could not find attribute WAERS and also dump showing below:
Category ABAP Programming Error
Runtime Errors UNCAUGHT_EXCEPTION
Except. CX_WD_CONTEXT
ABAP Program CL_WDR_CONTEXT_NODE_INFO======CP
Application Component BC-WD-ABA-RUN
Date and Time 21.05.2014 00:13:32
Short text
An exception occurred that was not caught.
What happened?
The exception 'CX_WD_CONTEXT' was raised, but it was not caught anywhere along
the call hierarchy.
Since exceptions represent error situations and this error was not
adequately responded to, the running ABAP program
'CL_WDR_CONTEXT_NODE_INFO======CP' has to be
terminated.
Any help please.
BR, SrihariYes, since the release of the current segment is 45 and you are now in a ECC6 system you cannot cancel the release (because there is no ECC6 version). Just use the add version button to create a new version for ECC6. Once you have that you can add fields and set the release to ECC6.
If you later on need to add more segements you can then cancel the release for your ECC6 segment and add the fields and set the release to ECC6 again (because you already have an ECC6 segment)
Hope that explains it,
Michael -
Processing overdue error during delta extraction from datasource 0CO_OM_CCA
Hi,
I'm getting "Processing overdue error" in BW while extracting delta from datasource 0CO_OM_CCA_9. all other extraction jobs from R3 -> BW are successful. Even Delta init on this datasource is successful & problem is only with delta package.
I appreciate if someone could provide information based on the following error details on this issue.
here are the extraction steps we followed.
Full load of fiscal years 2006 & 2007 Into transactional cube.
load budget data into transactional cube.
compression of the cube with "0 elimination"
Delta Initialization with fiscal period selections 1/2008 to 12/9999
all the above steps were successful.
and when delta package is scheduled, we are getting following errors.
BW system log
BW Monitoring job is turning red with following message.
Technical : Processing is overdue
Processing Step : Call to BW
Sending packages from OLTP to BW lead to errors
Diagnosis
No IDocs could be sent to the SAP BW using RFC.
System response
There are IDocs in the source system ALE outbox that did not arrive in
the ALE inbox of the SAP BW.
Further analysis:
Check the TRFC log.
You can get to this log using the wizard or the menu path "Environment -> Transact. RFC -> In source system".
Removing errors:
If the TRFC is incorrect, check whether the source system is completely
connected to the SAP BW. Check especially the authorizations of the
background user in the source system.
R3 Job Log
Even after BW job turns to red, R3 job continues to run for 2 hours and
eventually gets cancelled with an ABAP dump & here is the log.
Job
started
Step 001 started (program SBIE0001, variant &0000000110473, user ID
BWREMOTE) DATASOURCE = 0CO_OM_CCA_9
Current Values for Selected Profile Parameters
abap/heap_area_nondia.........2000000000 *
abap/heap_area_total..........2000000000 *
abap/heaplimit................20000000 *
zcsa/installed_languages......EDJIM13 *
zcsa/system_language..........E *
ztta/max_memreq_MB...........2047 *
ztta/roll_area................6500000 *
ztta/roll_extension...........2000000000 *
ABAP/4 processor: SYSTEM_CANCELED
Job cancelled
Thanks,
Hari Immadi
http://immadi.com
SEM BW AnalystHi Hari,
We were recently having similar problems with the delta for CCA_9. And activating index 4 on COEP resolved our issues.
Yes, by default there is a 2 hour safety interval for the CCA_9 DataSource. You could run this extractor hourly but at the time of extraction you will only be pulling postings through 2 hours prior to extraction time. This can be changed for testing purposes but SAP strongly discourages changing this interval in a production environment. SAP does provide an alternative described in OSS note 553561. You may check out this note to see if it would work for your scenario.
Regards,
Todd -
Error while executing Initialize with Data Transfer for 0FI_GL_10
Hello All,
Post Pre prod refresh, our timestamp for the datasource 0FI_GL_10 got reset. Due to which our deltas did not bring any records to the BW system.
First we did an Initialize without data transfer for all the BW related datasources. The deltas were then set properly for all datasources except 0FI_GL_10.
We then raised a message to SAP and they suggested to run the 'Initialize with data transfer' for 0FI_GL_10 so that the timestamp is set and accordingly the deltas are fixed.
The issue now is we are getting the following error message while running INIT with data transfer.
Job terminated in source system --> Request set to red
Message no. RSM078
We have copied the data till July 1st week of 2011.
Please advice. The issue is very critical.
Thanks & Regards
SnehaHi Arvind
Thanks for your inputs.
Please find below the details of the short dump.
Runtime Errors DBIF_RSQL_SQL_ERROR
Exception CX_SY_OPEN_SQL_DB
Date and Time 09/07/2011 11:25:32
Short text
SQL error in the database when accessing a table.
What can you do?
Note which actions and input led to the error.
For further help in handling the problem, contact your SAP administrator
You can use the ABAP dump analysis transaction ST22 to view and manage
termination messages, in particular for long term reference.
How to correct the error
Database error text........: "ORA-01652: unable to extend temp segment by 128
in tablespace PSAPTEMP"
Internal call code.........: "[RSQL/FTCH/FAGLFLEXT ]"
Please check the entries in the system log (Transaction SM21).
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
Information on where terminated
Termination occurred in the ABAP program "GP_GLX_FAGLFLEXT" - in
"FETCH_TO_ISTRUCTURE".
The main program was "SBIE0001 ".
In the source code you have the termination point in line 903
of the (Include) program "GP_GLX_FAGLFLEXT".
The program "GP_GLX_FAGLFLEXT" was started as a background job.
Job Name....... "BIREQU_4N3PZQ12IA0X0PYGEA85IG39S"
Job Initiator.. "BIWREMOTE"
Job Number..... 11203300
The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
procedure "FETCH_TO_ISTRUCTURE" "(FORM)", but it was neither handled locally
nor declared
in the RAISING clause of its signature.
The procedure is in program "GP_GLX_FAGLFLEXT "; its source code begins in line
840 of the (Include program "GP_GLX_FAGLFLEXT ". -
System Throws short dump while executing data source 2LIS_11_VASCL in RSA3.
Hello Experts,
I got short dump while executing data source 2LIS_11_VASCL in RSA3.
The details are as follow.
When importing object "MC11VA0SCL_TAB", the structure did not match the
structure of the target object. The error occurred in component
no. 567.
This may be due to one of the following reasons:
- the structure is actually different (the next field has, for
example, a different data type) or
- the same sequence of components were exported and imported,
but the fields were from other include units.
I have checked source and target fields and those are of same length and data type.
Could you please give some points why this short dump occurs.
Thanks
Konda ReddyHi,
This error is not between BI and R/3. It is within R/3. You may have setup data and then modified the datasource.
Delete setup data, generate your datasource again. Setup data and try again.
If you are on a live system with data setup after a downtime and you do not want to delete it, then bring your datasource to the original state when you setup data and pull data.
Cheers.... -
Error while extracting data from Generic datasource
Hello Gurus,
I have encountered an error "Errors in source system" with status red while extracting data from generic datasource into DSO.
I have done below things:-
1. Checked the jobs in source system, the job is successfully completed
2. The generic datasource is active and supporting delta with calender day in source system.
3. No TRfc error and no idocs stucked.
4. No short dumps in source system.
5. The delta queue(RSA7) is showing 0 with status as green.
6. Replicated the datasource On BW side and also activated the transfer rules by RS_TRANSU_ACTIVATE_ALL
The problem has not yet solved. Could you guys please suggest me what might be the reason for this error......
Thanks,
SonuHello,
I have used the generic delta using calender day.
Safety upper limit : - 1
Safety lowerr limit : - 0
I have made the entries in va01 transaction, but the delta queus is not getting updated which should show 1.
Do Generic extraction require any job to transfer data from Database table to delta queue.
We are not able to get the delta records on BW side. Please suggest.
Please suggest.
Thanks,
Sonu -
Dump during extraction for the custom datasource (ZFI_GL_14).
Hello all,
we are using Ecc 6.0 and we havent installed Enhancement Package 3. However our requirement is to create a custom datasource (ZFI_GL_14) similar to the standard one (0FI_GL_14). Initially we created the custom DS same as the standard one with the extraction method using Function Module. By default custom DS was assigned with extraction method F2. By running a program we changed F2 to F1 to resemble the standard one and made it as delta enabled as specified in the standard extractor.
when we started extracting the custom DS using RSA3, we encountered so many errors and resolved them. However still we are getting some more errors which requires your help.
1. While testing One of the function module FAGL_GET_LINE_ITEMS, it throws following ABAP dump.
Short text
| A dynamically specified FROM clause has an unexpected format.
|What happened?
| Error in the ABAP Application Program
|
| The current ABAP program "SAPLYPFI_FAGL_ITEMS_SELECT_BW" had to be terminated
| because it has come across a statement that unfortunately cannot be executed.
|Error analysis
| An exception occurred that is explained in detail below.
| The exception, which is assigned to class 'CX_SY_DYNAMIC_OSQL_SYNTAX', was not
| caught in
| procedure "YPFI_FAGL_GET_LINE_ITEMS" "(FUNCTION)", nor was it propagated by a
| RAISING clause.
| Since the caller of the procedure could not have anticipated that the
| exception would occur, the current program is terminated.
| The reason for the exception is:
| The running ABAP program attempted to execute an Open SQL statement in
which a FROM clause was specified dynamically in the field "LD_DBTAB_SYNTAX".
| In this
| FROM clause, either a table name after a join operator is missing, or an
| alias name after the key name "AS". The field "LD_DBTAB_SYNTAX" could be empty as well.
|Missing RAISING Clause in Interface
| Program SAPLYPFI_FAGL_ITEMS_SELECT_BW
| Include LYPFI_FAGL_ITEMS_SELECT_BWU01
| Row 1
| Module type (FUNCTION)
| Module Name YPFI_FAGL_GET_LINE_ITEMS
|Trigger Location of Exception
| Program SAPLYPFI_FAGL_ITEMS_SELECT_BW
| Include LYPFI_FAGL_ITEMS_SELECT_BWU01
| Row 353
| Module type (FUNCTION)
| Module Name YPFI_FAGL_GET_LINE_ITEMS
|Source Code Extract
|Line |SourceCde
| 323| lt_fields_flexgl
| 324| lt_fields_table1
| 325| lt_fields_table2
| 326| gv_si_table "erste Tab immer Flexgl?
| 327| gc_bkpf
| 328|* ' '
| 329| gc_bkpf_aedat
| 330| 'X'
| 331| CHANGING ld_dbtab_syntax
| 332| lt_fldlist_s
| 333| lt_where_tab[].
334
| 335|* open cursor
| 336| DESCRIBE TABLE lt_where_tab LINES ld_lines.
| 337| IF ld_lines GT 0.
| 338| delta_dbcnt = 0.
| 339| old_dbcnt = 0.
| 340| flag_cursor_open = 'X'.
| 341| cursor_flag = 'X'.
342
| 343| OPEN CURSOR WITH HOLD i_cursor FOR
| 344| SELECT (lt_fldlist_s)
| 345| FROM (ld_dbtab_syntax) CLIENT SPECIFIED
| 346| WHERE (lt_where_tab).
| 347| ELSE.
| 348| delta_dbcnt = 0.
| 349| old_dbcnt = 0.
| 350| flag_cursor_open = 'X'.
| 351| cursor_flag = 'X'.
352
|>>>>>| OPEN CURSOR WITH HOLD i_cursor FOR
| 354| SELECT (lt_fldlist_s)
| 355| FROM (ld_dbtab_syntax) CLIENT SPECIFIED.
| 356| ENDIF.
357
| 358| st_selection[] = lt_selection[].
| 359| st_fieldlist[] = lt_fieldlist[].
| 360| sd_dbtab_syntax = ld_dbtab_syntax.
| 361| st_fldlist_s[] = lt_fldlist_s[].
| 362| st_where_tab[] = lt_where_tab[].
| 363| st_seltable2[] = lt_seltable2[].
364
| 365| ENDIF. "cursor_flag
366
| 367| lt_selection[] = st_selection[].
| 368| lt_fieldlist[] = st_fieldlist[].
| 369| ld_dbtab_syntax = sd_dbtab_syntax.
| 370| lt_fldlist_s[] = st_fldlist_s[].
| 371| lt_where_tab[] = st_where_tab[].
| 372| lt_seltable2[] = st_seltable2[].
Line 353 contains the error.
1. L_DBTAB_SYNTAX. As per the statement this field should bring the table name, but it is not bringing any value whiledebugging.
2.also lt_fldlist_s should bring the field names.
As this is for New GL line item datasource, I am not sure what fields should lt_fldlist_s and what table name , and wheretab value should come , so that the function module can extract the data.
Kindly help me to get an insight into this issue and to get it resolved.
thanks,
Praba...Hi Frank,
yes I agree. That was the first question that came to me in my mind. However, the job was handed over to us, and we were able to exactly create the custom DS , FM and Function groups as similar to the standard one and everthing got activated perfectly. But during extraction, it throws the dump.While debugging, the function module is not able to pick the value for the 3 fileds which I stated above in one of my queries. The main extractor for this Datasource is FAGL_GET_SI_DATA and it uses the extract structure FAGLPOSBW.This Main function module in turn calls one more FM, FAGL_GET_LINE_ITEMS by exporting below parameters.
CALL FUNCTION 'FAGL_GET_LINE_ITEMS'
EXPORTING
i_block_data = 'X'
i_block_size = sd_max_lines
i_selection = lt_select_int
i_fieldlist = lt_fields_int
i_initflag = i_initflag.
ELSE.
From my observation , the above statements i_selection = lt_select_int and i_fieldlist = lt_fields_int should contain/pass the value to the line items FM, FAGL_GET_LINE_ITEMS.In the above thread also I mentioned I didnt get the value for ld_dbab_syntax, lt_fieldlst_s and ld_where_tab. I believe it is simply because i_selection and i_fieldlist is not getting the value from lt_select_init and lt_fields_init respectivelyImport parameters for this FM is as below.
I_BLOCK_DATA TYPE C
I_BLOCK_SIZE TYPE SY-TABIX
I_SELECTION TYPE GUSL_T_SELECTION
I_FIELDLIST TYPE GUSL_T_FIELDS
I_INITFLAG TYPE GUSL_BOOL
I_CHANGED_RECORDS TYPE GUSL_BOOL
export parameter for this FM is as below.
FLAG_CURSOR_OPEN TYPE FLAG
Changing parameter for this FM is as below
C_T_FAGLPOSE TYPE FAGLPOSE_T
where FAGLPOSE means Fields for Reading Data: Line Items: New General Ledger.GUSL_T_SELECTION is the same type like DDIC table type FB_T_FIELD_SELECT_OPTIONS which will have Fieldname and selection option range.GUSL_T_SELECTION is created within the type group GUSL as mentioned below.
TYPES: BEGIN OF GUSL_S_SELECTION,
FIELDNAME LIKE DFIES-FIELDNAME,
T_RANGE TYPE GUSL_T_RANGE,
END OF GUSL_S_SELECTION,
GUSL_T_SELECTION TYPE GUSL_S_SELECTION OCCURS 20.
wherein
FIELDNAME LIKE DFIES-FIELDNAME,
DFIES: --> DD Interface: Table Fields for DDIF_FIELDINFO_GET. Also GUSL_T_FIELDS refers to DFIES.
Regards,
Praba.. -
Stages when pulling data from CRM datasource?
Hi,
We are pulling data from CRM.Please explain me the steps while pulling data from CRM.Hi,
Data from CRM to BW is divided into diiferant Data sources.
First need to find data source name.
Use the following seps
First of all, activate the CRM DSs by scenario:
1) Activate the application component hierarchy (tcode RSA9). Changes made to the application component hierarchy in the CRM system can be transferred to the BW using the "Edit Application Component Hierarchy" (SBIW - Postprocessing of DataSources).
SAP Note 434886 must be implemented in CRM 3.0 before the application component hierarchy is activated.
2) Activate the Business Content DataSources (tcode RSA5).
Select/enter the application component and choose Execute (F8).
To compare the shipped and active versions, choose the 'Select Delta' pushbutton. If there is no active version of the DataSource, it is selected automatically.
To activate the shipped version, choose the 'Transfer DataSources' pushbutton.
3) Management of the versions of the BW-Adapter metadata (tcode BWA5). All DataSources are displayed that are managed by the BW Adapter.
As in transaction RSA5 (Service API Metadata Activation), the 'Select Delta' function can be used to select the inactive DataSources or compare shipped and active versions.
You can also go directly to the screen for maintaining DataSources that are managed by the BW Adapter.
The 'Compare Version' function makes a detailed comparison of the shipped and active versions.
All BW-Adapter metadata is considered when versions are compared:
Header information (Table SMOXHEAD)
Mapping information (Table SMOXRELP)
Global selection conditions (Table SMOXGSEL)
Attribute key fields (Table SMOXAFLD)
It is depends if you want to use in BW some ready made (Business Content) data analysis models.If so, you need to find your data source in RSA5 in CRM and activate it. See this link http://help.sap.com/saphelp_nw2004s/helpdata/en/04/47a46e4e81ab4281bfb3bbd14825ca/frameset.htm to find Cube you want to analyze in BW, and Data Source connected to it.
BW CRM analysis.
http://help.sap.com/bp_biv135/html/bw.htm
CRM Extraction
Pls chk this link for Crm enhancement
Enhance standard data sources in CRM
BWA1 is for all standard crm datsource maintaince
rsa2 for generic datasource
BWA5 i think we use this Tcode after RSA5 activation additionally.
yes(incase of delta)
BWA7 do we have to use this tcode along with BWA1 for standard datasources also or else only for generic datasource.
irrespective of the type of dtasource,use it if you want to load delta(you need to delta enable the datasource here)
So we don't need to put the code as we traditionally do it for R/3 , if we just mapp the fields that would bring the data for these fields.
as i told in CRM we willwrite code in BADI in case you have done enhancement
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/biw/a-c/customer%20enhancements%20and%20userexits%20in%20bw%20-%20sap%20netweaver%20%20know-how%20network%20webinar.pdf
also chk this(credit goes to the writer)
CRm enhancement:
1. Enhance Extract Structure with the required fields. (Create & include an append structure to the extract structure via transaction RSA6).
2.a) Release the fields of the append for usage. ( To do this, double click on the Datasource and remove the flags in the column 'Hide Field' for all fields of Append).
2.b) If the new fields cannot be seen in the extract structure of the transaction BWA1 then change and save the datasource, and then activate it in RSA6.
3. Define your mappings in BADI (CRM_BWA_MFLOW) to fill these fields.
Goto SPRO . Follow the path ->SAP Implementation guide ->Implementation with other mySAP components ->Data transfer to the Business Information Warehouse-> Settings for the application specific datasources (CRM)->Settings for BW adapter-> Badi :BW adapter :Enhancement of datasources in messaging flow.
4. Replicate the new Datasource to BW.
5. Expand the Communication Structure in BW.
6. Maintain transfer Rules for the new Datasource.
7. Activate the trasfer rules and perform the upload.
Refer to the SAP Note 692195 for more info ......
pls Check this links..
regarding bw crm extraction
http://help.sap.com/bp_biv235/BI_EN/html/BW/CRMAnalytics.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/be/92fb3b28904f73e10000000a114084/frameset.htm
CRM extraction
Hope this helps,
Regards
CSM Reddy -
Short Dump while execuition of DTP.
Hi,
I got short dump while execuiting the DTP.
Error messages shows as below:
1.The database returned a value containing an error
2.An exception with the type CX_SY_OPEN_SQL_DB occurred, but was neither handled locally, nor declared in a RAISING clause
3.Exception CX_SY_NO_HANDLER logged
Could you please help us in solving this issue.
Regards,
Suman.hi,
an error like this comes usually in 2 cases
1) not enough resources are available to carry out loads.in this case increase no of parallel processes to 2-3 in dtp setting,check the option get delta request by request(if its a delta load) and decrease packet size to 10000(from default 50000)
2)fileld to field assignment is not proper:
u need to check if there is any source field with lenth lets say 5 ans is getting assisgned to a target field length lets say 4.in this case dumps will come
please check the error message in st22 and here you can also check the termination point.please check in option Chosen variables /contents of system fileds where you can get temp values at point of termination.here you can pinpoint values at which prog is throwing dumps.
Maybe you are looking for
-
Looking for Pre-Rendered Editing / Color Grading Workflow suggestions.
Looking for Pre-Rendered Editing / Color Grading Workflow suggestions. All my material is rendered via RenderMan, our resolution is 1280x544, and our format is generally .exr in 32 bit space. Our editor has been converting over to 32-bit tiffs, and u
-
Which size gauge for gigaworks S750?
hello everyone, my 2 rear speakers need extending and i was wondering if anyone could help me out with what is the best wire gauge to go for, from what i can find i believe 2-6awg is best. i would go for the 2 but there is a massive price dif between
-
Order status -- need help from rep
I received an inbox message from a verizon wireless employee regarding my order. This was at 10:00AM yesterday. Could that person please respond to my messages? Thank you in advance. >> Subject edited for brevity and content moved to body of post <<
-
Human task expression builder (10.1.3.1 GA)
When I open up the Expression builder while inside the humanTask builder/editer/whatchamacallit I cannot see any BPEL variables. The Title displayed in the Expression builder is schema (vs the BPEL variables I see elsewhere). This gives me access to
-
WebService Unrecognized binding style error
I am trying to access a webservice method throught action Script. I just need to call a method " RequestSomeMethod"and send 2 parameters. But am getting following error : RPC Fault faultString="Unrecognized binding style 'null'. Only 'document' and '