Problem with COPA extractor 1_CO_PA ...

Hi all,
I am facing a problem with COPA extractor where delta is bringing in records which have been commited to database more that 6 hours ago. I understand that according to a note that COPA extractors have a default safety interval of 30 minutes but 6 hours is too much.
Is there any way I can change that? Is there any customizing option? Note 392876 explans how to change the safety interval to 5 minutes but I dont know if it is applicable for our patch level?
We are at PI->2004_1_500 patch SAPKIPZI69.
Also the safety limit is also maintained in ROOSOURCE-DELTASAFE2 field, should I just change it there?
any help is appreciated...
thanks

I see that you are not so novice!
Please, how can I check the time and time zone in R/3 and BW?
Thank you in advance

Similar Messages

Problem with COPA

Hi gurus.
I have a problem with PA.
My problem is that when i create a sales orden and i have a WBS Element i cant fill the Profit. Segment because those are reals.
How can i do to have these doble account assignement???
Thanks in advance

No, i dont want to reverse it.
The proble is that when i generate a sales order with WBS Element i cant fill the Profit. Segment. it is in grey due to a standard use of SAP.
i dont want to settle my WBS Element and put my WBS Element at zero.
How can ia have the sales order information in COPA with that????

Problem with this extractor 0BBP_TD_PO_1

Hi Experts,
We had seviour issue with this extractor. We are wokring on SRM5.0 using this:0BBP_TD_PO_1.Its not capturing the Delta records.Till now we are running through Init Package only. Please let me know how to resolve this issue. BI-Content support Pack:13.
Apreciate your time and help.
Thanks,
Rajendra.A

Hi
Please try these SAP OSS Notes ->
Note 652062 EBP 4.0-5.0: Contract interlinkage extractor & delta upload
Note 725171 EBP 4.0: No requester or supplier in delta extractor
Note 745537 EBP 3.0-4.0: PO extractor and header status
Note 809118 EBP 5.0: PO extractor and header status
Note 747208 EBP 3.5-5.0: PO extractor and DCI
Note 730389 EBP 3.5 SRM 4.0: PO extractor and tax code
Note 677697 EBP 35-40: Incorrect preceding document in PO extractor
Note 677524 EBP 20c-40: Dump in the ORG-extractor
Note 481283 Initializing the delta method in the EBP
Note 538695 EBP 3.5: BW extractor for bid invitation
Note 313595 Request cannot be updated directly in InfoCube
Hope this will help. Do let me know.
Regards
- Atul

Billing Document Releasing Problem with COPA

Hi,
While releasing the billing document,it is not releasing to accounting and giving the below error log.
Error Message number -KE/AD713
Note:
In the below error log it is saying that to activate the +/- sign in KE4I.But for some billing documents it didnot give any error like below.Why it is asking only for this billing document? Kindly help me.
Diagnosis
    When condition "ZSCM" (application "V") was transferred to the value field "VV139" in operating concern "AFCO" in Profitability Analysis, the following became apparent:
1.The condition can take both positive and negative   values
2.The flag "Transfer values with +/- signs" has not be set in Customizing for value field assignment.
    Inconsistencies in the data could occur as a consequence.
System Response
    It is not possible to post the document in Profitability Analysis.
Procedure
    Set the flag "Transfer values with +/- signs" for the condition "ZSCM".
    You should set the flag "Transfer values with +/- signs" selectively for individual conditions if:
1. The conditions can take both negative and positive values (for example, in the case of conditions that describe a transfer price surcharge or a loss deduction).
2. The conditions appear several times in a billing document and thus cause a debit posting as well as a credit posting (this is the case, for example, when creating or cancelling reserves).
By activating the flag "Transfer values with +/- signs", you balance the positive and negative values in a
condition. You can thereby guarantee that the sum of the negative and positive condition values is displayed as the correct total value in the value field assigned to the condition.
Caution when in the production system!
    If you have already used condition "ZSCM" to post data in the production system, then the sign in
    Profitability Analysis may differ from the previous sign as a result of the flag "Transfer values with +/-
    signs" having been activated. See the F1 Help documentation on the field "Transfer values with +/-
    signs" or the OSS note 52849. If deviating signs occur, it makes sense to move condition "ZSCM" to a new value field! Contact your system adviser or SAP.
Supriya

Hello,
The answer resides within your question itself.
Where you have assigned your condition type in log i.e., ZSCM, make sure that you have ticked +/- tick
IMG ==> Profitability Analysis ==> Flows of Actual Values ==> Transfer of Incoming Sales Orders
Assign Value Fields
Where you will find +/- check box. Make sure that you have checked the same.
Note: That the indicator transfer +/- is not used to compare the different use of plus or minus signs between FI or SD and CO-PA. If you activate the indicator, only the positive and negative values for the condition in question will be balanced. This guarantees that the sum of the negative and positive condition values are displayed as a correct total value in the value field assigned to that condition.
Tip: In order to perform transfer conditions from the billing documents the same definitions must be established for the vlaue fields in Profitability Analysis and both pricing and condition types must be defined in SD.
Please also read SAP note 52849 in this regard.
Regards,
Ravi

BAPI_ACC_DOCUMENT_POST - problem with COPA

Hi all,
I'm using the function BAPI_ACC_DOCUMENT_POST to post documents like F-02. It's working right, but it's not transfering to CO-PA. I'm trying to fill the table CRITERIA to pass values for proftability segment, but it's not working right for that.
I was filling CRITERIA for the follow fields, but I receive a error message in return of BAPI that says 'Complete PA structure ... ' :
    CLEAR I_BAPIACKEC9.
    I_BAPIACKEC9-ITEMNO_ACC = p_item.
    I_BAPIACKEC9-FIELDNAME = 'KNDNR'.
    I_BAPIACKEC9-CHARACTER = i_report-kunnr.
    APPEND I_BAPIACKEC9.
    CLEAR I_BAPIACKEC9.
    I_BAPIACKEC9-ITEMNO_ACC = p_item.
    I_BAPIACKEC9-FIELDNAME = 'ARTNR'.
    I_BAPIACKEC9-CHARACTER = i_report-matnr.
    APPEND I_BAPIACKEC9.
Could anyone send me an example of the function ( BAPI_ACC_DOCUMENT_POST ) using table CRITERIA to transfer data to COPA ?
Thanks

Hi Savitha,
follow the values in structures to call BAPI:
HEADER:
OBJ_TYPE      BKPFF
OBJ_KEY          $
OBJ_SYS           CTD600
BUS_ACT           RFBU
USERNAME      FERRATRE
HEADER_TXT     4400000325
COMP_CODE     7100
DOC_DATE     20060209
PSTNG_DATE     20060209
TRANS_DATE     00000000
FISC_YEAR     2006
FIS_PERIOD     08
DOC_TYPE     GG
BAPIACKEC9:
0000000002|ARTNR|000000000000530404
0000000002|KNDNR|0000080018
0000000002|SPART|10
0000000002|VKORG|BZ01
0000000002|VTWEG|10
BAPIACGL09:
ITEMNO_ACC     0000000002
GL_ACCOUNT     0000040000
DOC_TYPE     GG
FIS_PERIOD     08
FISC_YEAR     2006
PSTNG_DATE     20060209
VALUE_DATE     20060209
CUSTOMER     0000080018
TAX_CODE     SD
MATERIAL     000000000000530404
BAPIACCR09:
ITEMNO_ACC     0000000001
CURRENCY     BRL
AMT_DOCCUR     136.0000
MESSAGE ERROR FROM BAPI:
E|RW|609|Error in document: BKPFF $ CTD600
E|KF|018|Complete PA transfer structure FI
W|KI|350|Profitability segment being derived again

Performance problem with 0REFX_6 extractor

Hello,
I would like to use 0REFX_6 extractor.
If I select one fiscal period, it takes 7mn, for 2 fiscal periods 15mn, etc etc
Do you know you to speed the extraction ?
Best regards
Nicolas

Hi,
Check the notes 1026933 & 1280444.
Hope this helps,
Regards,
Rama Murthy.
Edited by: Rama Murthy Pvss on Dec 15, 2009 12:27 PM

Problem with the Extractor Framework Manager job

Hello 
The Diagnostics Setup scheulded a job: EFWK Resource Manager (01 Minute) 
This job has the status Finished, but the job log has the following entries every time: 
 
|Datum |Uhrzeit |Nachrichtentext |N-Klasse|N- Nummer|N-Typ| 
 
|05.01.2010|12:30:01|Job wurde gestartet | 00 | 516 | S | 
|05.01.2010|12:30:01|Step 001 gestartet (Programm E2E_EFWK_RESOURCE_MGR, Variante , Benutzername 01191042) | 00 | 550 | S | 
|05.01.2010|12:30:01|TPP 0020283456 E2E_ME_RFC_ASYNC W 3BDA34C6D1230D0C1988EE777FD22047 SOLMANDIAG DIA WP Resource Failure| 00 | 001 | S | 
|05.01.2010|12:30:01|SME E2E_ME_RFC_ASYNC W AF4891D11719ECEA2C8C872EFFA0CBFE SOLMANDIAG DIA WP Resource Failure| 00 | 001 | S | 
|05.01.2010|12:30:01|TAE 0020283456 E2E_ME_RFC_ASYNC W 4ADE7EA655B62C79DDC5D7F07A100190 SOLMANDIAG DIA WP Resource Failure| 00 | 001 | S | 
|05.01.2010|12:30:01|TAP 0020283456 E2E_ME_RFC_ASYNC W 55D9710E31D1A0E5A1B755DD156AC296 SOLMANDIAG DIA WP Resource Failure| 00 | 001 | S | 
|05.01.2010|12:30:01|SME E2E_ME_RFC_ASYNC W 6A293C886DC33BF281E22FCBAA8AFC23 SOLMANDIAG DIA WP Resource Failure| 00 | 001 | S | 
|05.01.2010|12:30:01|TAE 0020283456 E2E_ME_RFC_255 W B4AB19B6BC72E0E439B28F44BFEDA867 NONE DIA WP Resource Failure | 00 | 001 | S | 
|05.01.2010|12:30:01|TAE 0020283456 E2E_ME_RFC_255 W 76C2909D46B110F20E6232ECF903A4C8 NONE DIA WP Resource Failure | 00 | 001 | S | 
|05.01.2010|12:30:01|TAE 0020283456 E2E_ME_RFC_255 W B38E7C9401B23AEBE18C83E8C9D3F5F4 NONE DIA WP Resource Failure | 00 | 001 | S | 
|05.01.2010|12:30:01|TAT 0020283456 E2E_ME_RFC_ASYNC W 81615C7B80DFA63B4B79B5E78EF71648 SOLMANDIAG DIA WP Resource Failure| 00 | 001 | S | 
|05.01.2010|12:30:01|TAT 0020283456 E2E_ME_RFC_ASYNC W B170834A99DA28EB6A03F6040AFEDEE9 SOLMANDIAG DIA WP Resource Failure| 00 | 001 | S | 
|05.01.2010|12:30:01|TAE 0020283456 E2E_ME_RFC_255 W A34F9C87BED6D9B9DA57999B075A27F6 NONE DIA WP Resource Failure | 00 | 001 | S | 
|05.01.2010|12:30:01|TAP 0020283456 E2E_ME_RFC_ASYNC W A4A5DCFD278A0B8C58F20818B21B4AD8 SOLMANDIAG DIA WP Resource Failure| 00 | 001 | S | 
|05.01.2010|12:30:01|TAE 0020283456 E2E_ME_RFC_255 W FB734F3EC6956B0CB4FB314E4E9B6DAF NONE DIA WP Resource Failure | 00 | 001 | S | 
|05.01.2010|12:30:01|TAE 0020283456 E2E_ME_RFC_ASYNC W 3A60AAB77774D083779638F4596435F3 SOLMANDIAG DIA WP Resource Failure| 00 | 001 | S | 
|05.01.2010|12:30:01|TAE 0020283456 E2E_ME_RFC_255 W D90A359199E5341F425521A937462FA2 NONE DIA WP Resource Failure | 00 | 001 | S | 
|05.01.2010|12:30:01|TAE 0020283456 E2E_ME_RFC_255 W 0BEDDE4B4A2830F0305FDD27C2863CDF NONE DIA WP Resource Failure | 00 | 001 | S | 
|05.01.2010|12:30:01|TAE 0020283456 E2E_ME_RFC_255 W 1BDECD07CE3A30647BEF641D63938ED2 NONE DIA WP Resource Failure | 00 | 001 | S | 
|05.01.2010|12:30:01|TAE 0020283456 E2E_ME_RFC_255 W 12A2D39C4D127D4A1D492949748A9322 NONE DIA WP Resource Failure | 00 | 001 | S | 
|05.01.2010|12:30:01|SME E2E_ME_RFC_ASYNC W 90B2FA1D891342909D842B872214CEE3 SOLMANDIAG DIA WP Resource Failure| 00 | 001 | S | 
|05.01.2010|12:30:01|SME 0020216294 E2E_ME_RFC_255 W 1601AE3A069301A15C40CB2BE39AF7D5 NONE DIA WP Resource Failure | 00 | 001 | S | 
|05.01.2010|12:30:01|SME 0020216294 E2E_ME_RFC_255 W 77ED40F94D551BE6FCD2EB407CB889C5 NONE DIA WP Resource Failure | 00 | 001 | S | 
|05.01.2010|12:30:01|TAE 0020283456 E2E_ME_RFC_ASYNC_NO_RR W DDFB215F2DB21E36B388EFED001EF7AD NONE DIA WP Resource Failure| 00 | 001 | S | 
|05.01.2010|12:30:01|SME 0020216294 E2E_ME_RFC_255 W B0F6FA11BD859F58C53D6CDD194B98F2 NONE DIA WP Resource Failure | 00 | 001 | S | 
|05.01.2010|12:30:01|SME 0020216294 E2E_ME_RFC_255 W E7AB58CA48F77908A091E4BB69C97D23 NONE DIA WP Resource Failure | 00 | 001 | S | 
|05.01.2010|12:30:01|SME 0020216294 E2E_ME_RFC_255 W C5A147B4A1A9E31648F4E35E2440AFB8 NONE DIA WP Resource Failure | 00 | 001 | S | 
|05.01.2010|12:30:01|SME 0020216294 E2E_ME_RFC_255 W F03F645E2383340067151874C9554569 NONE DIA WP Resource Failure | 00 | 001 | S | 
|05.01.2010|12:30:01|SME 0020216294 E2E_ME_RFC_255 W BA03B0B20E4E2CA82EDCE3C8617DB302 NONE DIA WP Resource Failure | 00 | 001 | S | 
|05.01.2010|12:30:01|SME 0020216294 E2E_ME_RFC_255 W A75C5EF7093960975F3BD2F3439F08D2 NONE DIA WP Resource Failure | 00 | 001 | S | 
|05.01.2010|12:30:01|SME 0020216294 E2E_ME_RFC_255 W 876055010DC7B9B9B838535BF1A303CF NONE DIA WP Resource Failure | 00 | 001 | S | 
|05.01.2010|12:30:01|TPP 0020283456 E2E_ME_RFC_ASYNC W 27C6C5A2C4A25C8B5CA58FA838976DA0 SOLMANDIAG DIA WP Resource Failure| 00 | 001 | S | 
and so on..
 
 
 
1.) I think that the job doesn't run right. 
2.) The jobs write every hour 100Mb in our Filesystem. 
 
Have anybody an idea, what my problem is and i can solve it? 
 
Thanks for help 
 
Olli

Hi Krishna
our ST version is SAPKITL430 and that's why the note is implemented.
In the screen of the Allocated Resources i see only two RFC Resources:
RFC Resources <NONE> Allocated <1> Total Capacity <1>
RFC Resources <SOLMAN_DIALOG_WORKPROCESSES> Allocated <1> Total Capacity <8>
Have you another idea
Regards
Oliver

Basic customizing for COPA extractors

Hi,
we are working on account-bassed CO-PA extractors of SAP ECC 6.0 in order to be able to analize finance data in BW7.0.
We are having problems with the extractor so, I need help for the basic customizing of COPA because we are having the following errors:
Error KM 443: No profile has been assigned (TKA01-CVPROF) to controlling area HHSC.
Error GP 526: Version 0 is not set up for controlling area CO = FR01.
Any help will be welcome.
Best regards.

Hi Monica
There is a whole bunch of BCsets which have been arranged in a heirarchical order as per the way they should be implemented in the standard system. They have all the settings to set up WH 0001 with structure, product, HU etc. The main BC set which has this is '/SCWM/BASICS'. This is a heirarchial BC set which has all the required config step by step.
Further more there are specific BC sets for setting up the standard config for inbound and outbound deliveries - '/SCWM/DLV_INBOUND' & '/SCWM/DLV_OUTBOUND'.
You can use these to get the basic config in place.
Hope this helps.
Thanks and regards
Deepak Joshi

Problem with extractor 1_co_pa

Hello experts
I have a copa extractor 1_co_pa_dge1 which is not extracting perticular range of Cost Elements in range 45000 to 45999.
Do we need to configure anything for this extractor in ECC to include all cost elements we need?
Whats configuration needed to be done for this extractor?
Regards
Sudeep

Hi Sudeep,
What the COPA extractor extracts would depend on the CO-PA functionality set in ECC..how the Operating concern is designed by the funtiional folks.....and the COPA datasource created from transaction KEB0.
We would only be able to extract data which exists in the table CE1**** (* is your operating concern). This is the actual line items table. CE2**** has plan data. Check if the data you are looking for exists in the tables, if not it is not our issue.

CO-PA, problem with extractors. (Account Based)

Hi everybody,
I have a problem when I want to execute RSA3, on the extractors that automatically generate the systems. I followed all the step that the document say, I belive.
1.- <KEB0>, I still use mandatory fields PERIO and KOKRS.
2.- <KEDV>. I put on the all fields a * , with exceptions KOKRS. (on it put the variable Controlling Area).
3.- <KEDU> Summarization levels.
3.1- Delete an regenerate
3.2- Refresh. (In this point I show that the systema take very short time, and when check with transactions KEDV, I can see that the refresh records are cero (0).
4.- Modify on SE11, the tables COEP and COEJ the index 4.
5.- <RSA3>, finally with the parameters, as example :
KOKRS: CO01
PERIO: 2006004,
The systems show a error.
I cant execute the extractors.
So , I know that is a problem with R3, but I don't use it if I dont want to use BW.
Some one knows the problems or the other steps that I forget to execute?
I appreciate your help,
regards,

HI,
To understand, why system behaving like this, you can analyze derivations in KEPM (Extras-> Analyze derivations). Try to enter manually using parameter set and then do Extras->Analyze derivation.
You could also try chaing the Target fied attributes to 'Overwrite with new value only if new value found' from 'Do no overwrite' in KEDR for your Table look up step.
Hope this helps.

Problem with extractors after system copy

Hi Gurus!
After system copy I have problem with export data source from infocubes. Logical system name was converted with BDLS. When I check any export datasource (8*) with transaction RSA3 system tell me that no data records was found though data in fact table every infocube exist (in SE11). What can I do to solve this problem?
Thanx.

Hi,
Of course I tried reactivate myself source system but problem is still here. When I check extractor (with RSA3) of any data source of any infoobject (master data) - everything is OK. When I check extractor for export data sorce - I have problem.
to Mickael: In modeling every thing is OK.
Thank you for all answers.....

HT203200 Is there a problem with redeeming movies from itunes? I purchased some movies with digital copies. But I can not download, due to Code redemption being temporary unavailable for the past 2 days.

Is there a problem with redeeming movies from itunes. I purchased some movies with digital copies. But i can not download movies, due to code redemption being temporary unavailable.

Hi there Cedric!
I have an article here for you that I believe will help you out with this issue by reporting it to iTunes. That article can be found right here:
How to report an issue with your iTunes Store, App Store, Mac App Store, or iBookstore purchase
http://support.apple.com/kb/HT1933
Thanks for being a part of the Apple Support Communities!
Regards,
Braden

A problem with 1CL_OLIS002 and 1CL_OMAT001 extractors - delta extraction

Hi
I have a problem with 1CL_OLIS002 and 1CL_OMAT001 extractors - delta extraction.
Interrelated extractors: 2LIS_11_VAITM and ZMATBATCH_Attr work well.
For 1CL's extractors I see current data in RSA3 but I don't see LUWs in RSA7.
Extractors send 0 records to BW.
There is no entry in "BIREQU* " job logs like this:
"Call customer enhancement BW_BTE_CALL_BW204010_E (BTE) with xxx records".
which I find in job logs when all worked well.
We had some problems with R3. I had to restart job "LIS-BW-VB-APPLICATION_13*".
May be it has influence on these extractors?
Any suggestions about how to resolve the problem?
Regards
PWnuk

Hi
Can you please share the solution of this problem with me,I am also facing same issue of Delta not working but full load is working in 1CL_OBI_001?
Edited by: Aseem84 on Jan 12, 2011 10:23 AM

Function module based generic extractor - Problem with the selection

Hi all
The following is my code in the function module. I am able to get the entire data if i dont give any selections and the number of records is also correct. But when i select a MATNR value, it returns 0 records where as it needs to return 3 records. If i give selection based on bukrs, werks, lgort its working fine. But if i give selection based on MATNR, then it is not working.... I think there is a problem in the bold part of my code. If i debug, LS_MATNR is having the correct value which indicates that there is no problem with the value being passed to LS_MATNR from my selection screen of my datasource in RSA3. Even GT_WERKS is also having data. Please help.
OPEN CURSOR WITH HOLD S_CURSOR FOR
SELECT MARA~MANDT
        MARA~MATNR
        MARC~WERKS
        MARD~LGORT
        MARA~MEINS
        MARD~LABST
        MARD~EINME
        MARD~SPEME
        MARD~RETME
        MARD~INSME
        MARD~UMLME
        MARD~VMLAB
        MARD~VMEIN
        MARD~VMSPE
        MARD~VMRET
        MARD~VMINS
        MARD~VMUML
        MARC~XCHPF
        MARD~KLABS
        MARD~KEINM
        MARD~KSPEM
        MARD~KINSM
from MARA inner join MARC on
MARAMANDT = MARCMANDT AND
MARAMATNR = MARCMATNR
inner join MARD on
MARAMANDT = MARDMANDT AND
MARAMATNR = MARDMATNR
AND MARCWERKS = MARDWERKS
for all entries in gt_werks
where MARC~werks EQ gt_werks-werks
AND MARA~MATNR in LS_MATNR.
    ENDIF.                             "First data package ?
Fetch records into interface table.
named E_T_'Name of extract structure'.
    FETCH NEXT CURSOR S_CURSOR
               APPENDING CORRESPONDING FIELDS
               OF TABLE E_T_DATA
               PACKAGE SIZE S_S_IF-MAXSIZE.

try this
select marc~matnr MARC~WERKS into t_marc for all entries in gt_werks
where werks EQ gt_werks-werks and lvorm = space.
if t_marc is not initial.
select MARD~LGORT MARD~WERKS MARA~MEINS MARD~LABST MARD~EINME
MARD~SPEME MARD~RETME MARD~INSME MARD~UMLME
MARD~VMLAB MARD~VMEIN MARD~VMSPE MARD~VMRET
MARD~VMINS MARD~VMUML MARC~XCHPF MARD~KLABS
MARD~KEINM MARD~KSPEM MARD~KINSM MARA~MEINS from
mard inner join MARA on mard~matnr = mara~matnr
for all entries in t_marc where mard~matnr = t_marc-matnr and mard-werks = t_marc-matnr
and mard~lvorm = space.

How to change safety interval in COPA extractor

Hi, guys!
I had a problem with changing safety interval in COPA extractor. I created COPA datasource using keb0. In RSA2 it can only view security interval. It is 1800 sec by default. I cannot change it.
How can I change it? I cant do it in RSO2, because it is not true generic delta.
Note 808663 is not implemented (we have higher patch on R/3). Delta extraction is correct, but safety interval is very annoying
Please help.
Message was edited by: Emerald

Thanks. I'll try to.
I thought I should edit ROOSOURCE, but it's maintainable in productive system.
Should I reInit delta after corrections implementation?

Problem with COPA extractor 1_CO_PA ...

Similar Messages

Maybe you are looking for