Data packaged 1: arrived in BW; processing: 2nd processing step not yet....

HI gurus,
I have a problem with de BW upload from R3 system. Till last week everything worked perfectly and automatic, but we added some companys to the system R3 and now, everyday the job is doing problems and we have to launch manually.
All data is transferred correctly to BW but then is not posted on PSA and in the details we have the following error message:
data packaged 1: arrived in BW; processing: 2nd processing step not yet finished
Have someone some idea about it?
THanks in advance.

Yes, it's like you wrote. When i execute manually it works ok. The problem is when it is working automatically in background, the daily work.
I don't have any dump (st22) in BW or R3. I checked also WE05, BD87, SM58 and others and everything looks fine.
thanks for the answer..

Similar Messages

Data Package 1 arrived in BW ; Processing :2nd processing step not finished

I am currently working on BI 7 and trying to pull data from r/3.
I have succesfully loaded the data into the PSA and now when i try updating the data (only 66 records, its a init run) into an ODS, but the system is taking a long time. On monitor Details in
Extraction:Errors occured.(with a delta warning sign), and
Transfer:Data Package 1 arrived in BW ; Processing :2nd processing step not finished.
On status Tab its yellow with message : Correct data request; processing running.
Hope i have made it clear.Please help.

Hi,
I will suggest you to check a few places where you can see the status
1) SM37 job log (give request name) and it should give you the details about the request. If its active make sure that the job log is getting updated at frequent intervals.
2) SM66 get the job details (server name PID etc from SM37) and see in SM66 if the job is running or not.
3) RSMO see what is available in details tab. It may be in update rules.
4) ST22 check if any short dump has occured.
Once you identify you can rectify the error.
If all the records are in PSA you can pull it from the PSA to target. Else you may have to pull it again from source infoprovider.
If its running and if you are able to see it active in SM66 you can wait for some time to let it finish. You can also try SM50 / SM51 to see what is happening in the system level like reading/inserting tables etc.
If you feel its active and running you can verify by checking if the number of records has increased in the new data table.

Data Package 1 : arrived in BW ; Processing : Selected number does not agre

Hi experts,
When loading data into PSA via UD Connect, getting the following error:
Overall status: Errors occurred: or: missing messages   -
(red light)
Requests (messages): Everything OK -
(green light)
   Data request arranged -
(green light)
   Confirmed with: 确定 -
(green light)
Extraction (messages): Errors occurred -
(red light)
   Data request received -
(green light)
   Data selection scheduled -
(green light)
   Error occurred in the data selection -
(red light)
Transfer (IDocs and TRFC): Missing messages or warnings -
(yellow light)
Data Package 1 : arrived in BW ; Processing : Selected number does not agree with transferred n -
(yellow light)
Processing (data packet): Everything OK -
(green light)
Data Package 1 ( 20000 Records ) : Everything OK -
(green light)
Please help me to resolve this problem, thanks in advance.
Gavin

Hi,
You must have the following profiles to BWREMOTE or ALEREMOTE users.So add it. Bcoz either of these two users will use in background to get extract teh data from ECC, so add tehse profiels in BW.
S_BI-WHM_RFC, S_BI-WHM_SPC, S_BI-WX_RFC
And also check the following things.
1.Connections from BW to ECC and ECC to BW in SM59
2.Check Port,Partner Profiles,and Message Types in WE20 in ECC & BW.
3.Check Dumps in ST22, and SM21.
4.If Idocs are stuck i.e see the OLTP Idoc numbers in RSMO Screen in (BW) detials tab see in bottom, you can see OLTP Idoc number and take the Idoc numbers and then goto to ECC see the status in WE05 or WE02, if error then check the log else goto to BD87 in ECC and give the Idoc numbers and execute manually and see in RSMO and refresh.
5.Check the LUWs struck in SM58,User Name = * (star) and run it and see Strucked LUWs and select our LUW and execute manually and see in RSMO in BW.
See in SDN
Re: Loading error in the production system
Thanks
Reddy

DataPackage1:arrived in BW, Processing 2nd processing step not yet finished

Hi BI-experts!
I would like to load e.g. transaction data from SAP ECC system into SAP BI system.
The Loading process is hanging in processing step u201CSERVICE APIu201D.
The process in hanging in status "yellow" and then changed after a while to status u201Credu201D.
[0FI_AR_4 |http://www.file-upload.net/view-1447743/0FI_AR_4.jpg.html ]
The following steps within Load process are yellow and then red:
Extraction (messages): Missing messages
Missing message: Request received
Missing message: Number of sent records
Missing message: Selection completed
Transfer (IDocs and TRFC): Missing messages or warnings
Request IDoc : Application document posted (is green)
Data Package 1 : arrived in BW ; Processing : 2nd processing step not yet finished
Info IDoc 1 : sent, not arrived ; Data passed to port OK
Info IDoc 2 : sent, not arrived ; Data passed to port OK
Info IDoc 3 : sent, not arrived ; Data passed to port OK
Info IDoc 4 : sent, not arrived ; Data passed to port OK
Subseq. processing (messages) : Missing messages
Missing message: Subseq. processing completed
DataStore Activation (Change Log) : not yet activated
Question:
Can some one tell me whether my distribution model or other settings are wrong?
I created 2 distribution model (BD64), one from SAP BW system and other from SAP BI system with message types RSRQST, RSINFO, RSSEND
Thank you very much!
Holger

Hi!
Many thanks for your response.
The tcode WE05 on source system showing the following:
Inbox IDoc's: RSQRST (amount: 1)
Outbound IDoc's: RSINFO (amount: 4)
When I go to SAP BW System (tcode WE05) i cannot detect any Inbound IDOC's of message type RSINFO.
What is wrong in my configuration?
Thank you very much!

Vendor return process for consignment stock not yet own by you

Hello guru,
I need some help from you on the following type of vendor return.
We receive vendor consignment goods into our warehouse and we notice we would like to return back to the vendor after several defects
defect were spotted few month later, how to execute vendor return like this given that the stock still own by the vendor
in accounting perspective?
Should I just create another PO and flag the return indicator and perform a movement 161 in MIGO? Is this method workable way
of doing this?
What if we need a delivery document to be generated after 161 movements is posted in MIGO?
Appreciate it.
Tuff

Hi,
   The vendor consignment stock has no accounting impact till the stock is issued to own stock or consumed (411K or 201K movement).
   Standard SAP recommends to use direct return delivery using 122 movement in MIGO to return the consignment stock material back to vendor.
   If you still wanted to proceed with return PO, then maintain the message ME640 as warning message (W) in the path: OLME - Environment Data - Define Attributes of System Messages - System messages. Now, create a return PO and create GR against the return PO.
   If you want proceed with SD route for returning to vendor, refer the thread: Return PO with Text material shipping tab
Regards,
AKPT

BW: Data Packages Selected number does not agree with transferred

Hi,
I am running into an issue with an existing master data text load process chain in Production. The extractor is from ERP and there are only 159 records. What is happening is the chain is stuck on yellow but there is an issue with the data packages. The status error message is 'Missing data packages for PSA table'. Clicking into the Details tab the message then states Data Package 1: arrived in BW; Processing: Selected number does not agree with transferred.
The version is BI 7.0. I have done the following steps and still no luck. Looking for any suggestions. Thanks.
ERP
    SM37 (Job always finishes)
    SM58 (No IDOCS stuck)
    ST22 (No short dumps)
BW
    SM58 (No IDOCS stuck)
    SM37 (Job always finishes)
    ST22 (No short dumps)
Reactivated Datasource: RSDS_DATASOURCE_ACTIVATE_ALL
Reactivated Transformation: RSDG_TRFN_ACTIVATE

Hi
Just check whether source system connection is ok in RSA1.
if it is fine then have a loo at the below thread(last post)
Data Load from R/3 to BW-'Selected number does not agree with transferred'
Regards,
Venkatesh

Every 3rd data package taking long time for execution

Hi Everyone
We are facing a strange situation. Our scenario involves doing a full load from DSO to CUBE.
Start routines are not very database intensive and care has been taken to write them in a optimized way.
But strangely every 3rd data package is taking exceptionally longer time than other data packages.
a) DTP is having 3 parallal processes.
b)time spent in extraction , rule, and updation is constant for every data package.
c)start routine time is larger for every 3rd data package and keeps on increasing. for e.g. 5 mins, 10 mins, 24 mins, 33 mins etc it increases by each 3rd package.
I tried to anlayze the data which was taking so much time but found no difference in terms of data in normal and longer time taking DTP (i.e. there was not logical difference in data for start routine to behave like this).
I was wondering what can be the possible reasons for it and may be some other external system factors can be responsible for it. If someone can help in this regard that will be highly appreciated.

Hi Hemanth,
In your start routine, are you by any chance adding or multiplying the number of records to the source_package? Something like copy source package into an internal table, add records to internal table and then copy it back to source package? If some logic of this sorts is in your start routine, you need to refresh your internal table. Otherwise, the internal table records goes on increasing with every data package. So, the processing time might increase as the load progresses. This is one common mistake I have seen. Please check your code if you have something like that and refresh the internal tables. See if this makes any difference.
Thanks and Regards
Subray Hegde

Data package size

What is the basic difference between RSCUSTV6 & SBIW->General setting ->Maintain Control parameters in relation of modification of data package format.

Hi,
Just see the help on
Maintain Control Parameters for Data Transfer:
1. Source System
Enter the logical system of your source client and assign the control parameters you selected to it.
You can find further information on the source client in the source system by choosing the path
Tools -> Administration -> Management -> Client Maintenance.
2. Maximum Size of the Data Package
When you transfer data into BW, the individual data records are sent in packages of variable size. You can use these parameters to control how large a typical data packet like this is.
If no entry was maintained then the data is transferred with a default setting of 10,000 kBytes per data packet. The memory requirement not only depends on the settings of the data package, but also on the size of the transfer structure and the memory requirement of the relevant extractor.
3. Maximum Number of Rows in a Data Package
With large data packages, the memory requirement mainly depends on the number of data recrods that are transferred with this package. Using this parameter you control the maximum number of data records that the data package should contain.
By default a maximum of 100,000 records are transferred per data package.
The maximum main memory requiremen per data package is approximately 2 Max. Rows 1000 Byte.
4. Frequency
The specified frequency determines the number of IDocs that an Info IDoc is to be sent to, or how many data IDocs an Info Idoc describes.
Frequency 1 is set by default.. This means that an Info Idoc follows every data Idoc. In general, you should select a frequency between 5 and 10 but no higher than 20.
The bigger the data IDoc packet, the lower the frequency setting should be. In this way, when you upload you can obtain information on the respective data loading in relatively short spans of time .
With the help of every Info IDoc, you can check the BW monitor to see if there are any errors in the loading process. If there are none, then the traffic light in the monitor will be green. The Info IDocs contain information such as whether the respective data IDocs were uploaded correctly.
5. Maximum number of parallel processes for the data transfer
An entry in this field is only relevant from release 3.1I onwards.
Enter a number larger than 0. The maximum number of parallel processes is set by default at 2. The ideal parameter selection depends on the configuration of the application server, which you use for transferring data.
6. Background job target system
Enter the name of the application server on which the extraction job is to be processed.
To determine the name of the application server, choose
Tools -> Administration -> Monitor -> System monitoring -> Server. The name of the application server is displayed in the column Computer.
7. Maximum Number of Data Packages in a Delta Request
With this parameter, you can restrict the number of data packages in a delta request or in the repetition of a delta request.
Only use this restriction when you expect delta requests with a very high data volume, so that, despite sufficiently large data package sizes, more than 1000 data packages can result in a request.
With an initial value or when the value is 0, there is no restriction. Only a value larger than 0 leads to a restriction in the number of data packages. For reasons of consistency, this number is not generally exactly adhered to. The actual restriction can, depending on how much the data is compressed in the qRFC queue , deviate from the given limit by up to 100.
RSA6:
Used to change the Datapacket Size.
Thanks
Reddy
Edited by: Surendra Reddy on Mar 12, 2010 6:27 AM

Data package

I am about to upgrade my basic phone and was thinking about a blackberry, however it says i need some expensive data package? MY friend had a blackberry and chose not to pay for it. I really like the phone is there any way I can get it and use it as a regular phone no data package?

In order to activate a blackberry on the Verizon network you will need to subscribe to a data package 30/50/80 dollars
No smartphone can be on their network without it. I'm sure once you have it you will end up doing more things with your phone than you do now

Data Package 000001 : sent, not arrived. No data load in BW 7

Hi gurus...i am working with BW 7 and i have already had the complete data flow from SRM to BW, some Business Content extractors and somo others generic extractors. We have created transformations, info packages and DTP's, in fact we have loaded master data and transactional data but since last monday data load is not working any more, now every time we manually run the infopackage the next waring message appears:
Data Package 000001 : sent, not arrived
and the data load just wait for an answer of SRM (with is the source system) or SRM waits a request from BW.
We have reactivated the extractors in the SBIW, replicated and reactivated in BW (also we reactivate the transformations) and the data load is not working. Then we also regenerate the Data source but it does not work.
Do you have and idea of what is happening or which could be the problem.
Thanks

Check in transaction SMQA in the source system. The communication might not be working. If there are any entries in RED, then select execute LUWs from the menu to manually process them.
Read the error and try to resolve it before though.

Maximum package size for data packages was exceeded and Process terminated

Hello Guru,
When i am execute the process chain i got this message Maximum package size for data packages was exceeded and Process terminated,any body help to me in this case how can i proceed.
Thanks & Regards,
Suresh.

Hi,
When the load is not getiing processed due to huge volume of data, or more number of records per data packet, Please try the below option.
1) Reduce the IDOC size to 8000 and number of data packets per IDOC as 10. This can be done in info package settings.
2) Run the load only to PSA.
3) Once the load is succesfull , then push the data to targets.
In this way you can overcome this issue.
You can also try RSCUSTV* where * is an integer to change data load settings.
Change Datapackage size for extraction, use Transaction RSCUSTV6.
Change Datapackage size when upload from an R/3 system, set this value in R/3 Customizing (SBIW -> General settings -> Control parameters for data transfer).
IN R/3, T-Code SBIW --> Genaral settings --> Maintain Control Parameters for Data Transfer (source system specific)
Hope this helps.
Thanks,
JituK

Error In DTP:Data package 1 / XDateX XTimeX Status 'Processed with Errors'

Hi,
While Pushing the data from the DSO(0PP_DS01 - Planned/Actual Comparison Order/Material View) to Cube 0PP_C15 -( Backlogged Production Orders).
Getting the Error as : Data package 1 / XDateX XTimeX Status 'Processed with Errors'
When checked the Long text it shows the same text i.e.,Data package 1 / XDateX XTimeX Status 'Processed with Errors'
It does not show any further error message which i can point out.
If anyone has come across this error please provide the resolution.
Thanks,
Adhvi Rao

Hi Advirao,
Are you using DTP to load the data to the target? Then you can enable error stack to collect the erroneos records.
Also check if you have activated the request in ur source DSO.
Regards
Dinesh

Data packet not yet processing in ODS load??

Hi all,
I got an error when I loaded data from IS to the ODS. Can someone let me know why and how to resolve it. Thank you in advance.
Here is the error message in the monitor:
Warning: data packet 1 & 2 arrived BW; processing: data packet not yet processing.
(No data packet numbers could be determined for request REQU_77H7ERP54VXW5PZZP5J6DYKP7)
Processing end:
transfer rules (0 record): missing message
Update PSA (0 record): messing messages
Update rules (0 record): messging messages

John,
I dont think its space problem.In st22 go with detail note.
What happend, how to correct it.Will help you to solve the problem.
Check this note 613440 also.
Note : 647125
Symptom
A DYNPRO_FIELD_CONVERSION dump occurs on screen 450 of the RSM1 function group (saplrsm1).
Other terms
DYNPRO_FIELD_CONVERSION, 450, SAPLRSM1
Reason and Prerequisites
This is caused by a program error.
The screen contains unused, hidden fields/screen elements that are too small for the screen check that was intensified with the current Basis patch (kernel patch 880). These fields originate in the 4.0B period of BW 1.0 and are never used.
Solution
Depending on your BW system release, you must solve the problem as follows:
BW 3.0B
 ImportSupport Package 14 for 3.0B (BW 3.0B Patch 14 or SAPKW30B14) into your BW system. This Support Package will be available when note 571695 with the short text,"SAPBWNews BW 3.0B Support Package 14", which describes this Support Package in more detail, is released for customers.
BW 3.1 Content
 ImportSupport Package 8 for 3.1 Content (BW 3.10 Patch 08 or SAPKW31008) into your BW system.This Support Package will be availablewhen note 571743 with the short text, "SAPBWNews BW 3.1 Content Support Package 08", is released for customers.
The dump occurs with the invisible G_NEW_DATUM date field on the bottom right of the screen, which is only 1 byte long and can be deleted.
You can delete the following unused fields/screen elements:
%A_G_NEW_NOW Selectionfield group
G_NEW_ZEIT Input/output field
G_NEW_UNAME Input/output field
G_NEW_DATUM Input/output field
%#AUTOTEXT021 Text field
G_NEW_NOW Selection button
G_NEW_BATCH Selection button
You can delete these fields/screen elements because they are not used anywhere.
This deletion does not cause any problems.
After you delete the fields/screen elements, you must also delete the following rows in the flow logic in screen 450:
FIELD G_NEW_DATUM MODULE DOKU_NEW_DATUM.
FIELD G_NEW_ZEIT MODULE DOKU_NEW_ZEIT.
The function group is then syntactically correct.
Unfortunately, we cannot provide an advance correction.
The aforementioned notes may already be available to provide information in advance of the Support Package release.However, the short text will still contains the words "preliminary version" in this case.
For more information on BW Support Packages, see note 110934.
Thanks
Ram

Missing data packages for PSA Table in sap netweaver 2004s

When we tryed to load the master data 0customer we have got the message
"Information Idoc: Sent, but did not arrive:
Missing data packages for PSA Table
Diagnosis
Data packets are missing from PSA Table . BI processing does not return any errors. The data transport from the source system to BI was probably incorrect.
We couldn't find any entries in source system.We have checked the tablespaces and authorizations.Its looks good.
WE have replicated and tryed again.But still getting the same error message.
we have SAP_BASIS
Release 700,level 0008, Highest SAPKB70008 basis component.
pls help us with the solution.
Thanks in advance.
-Soujanya

Hi
1) goto BD87 Tcode... take ur Idoc number and check the status of the idoc if it is 64 .. just process it manually ....
2) go to the TRFC in Datawarehouse and execute the LUWs manually ..
hope it helps
regards
AK
************assign points if usefull******

Identify the last data package in start routine

Hi Everyone
We have a start routine in transformations. We require to do some special processing in the start routine only when the last data package is executing. How can we determine in the start routine that current package is last one or not ? Any pointers in this direction are appreciated.

Hi,
You can get packet Id from datapackid in start routine and end routine. But I'm not so sure how to identify the last packet ID, alternatively you can store this packet id in some where else and read the same value in End routine if your logic(processing) permits to do this in End routine instead of Start routine.
METHODS
      start_routine
        IMPORTING
          request                  type rsrequest
          datapackid               type rsdatapid
        EXPORTING
          monitor                  type rstr_ty_t_monitors
        CHANGING
          SOURCE_PACKAGE              type tyt_SC_1
        RAISING
          cx_rsrout_abort.
hope it helps...
regards.
Raju

Data packaged 1: arrived in BW; processing: 2nd processing step not yet....

Similar Messages

Maybe you are looking for