Idocs not processed automatically in BW

Dear Experts,
I have a scenario here where I extract data from source system via process chains.
The source system job completed and in BW, the outbound idocs resulted in the following Status (02).
02 Error passing data to port 1
In the infopackage message dialog, I got the message as
Could not find code page for receiving system
Errors have been reported in Business Information Warehouse during the IDoc update:
In order to resolve this, I'm manually processing the idoc using program RBDAGAIN.
Note: This issue occurs only when I trigger the infopackage via process chains.
How do I rectify this error so that the idocs are processed automatically in BW?
Br, Harish

Hi,
how much time your ecc job takes to finish job.
Is this process chain newly created one or old one?
if its old one, any changes were applied on this process chain recently?
is it showing any idoc numbers at below status bar.
if yes then try to pull them by using t code BD87.
Can you share info pack error message screen shot.
Thanks

Similar Messages

Queues, not processed automatically they are status Ready

Hi Experts ,
Queues in outbound(smq2), not processed automatically they are status Ready from long time, RFC is working fine
i tried to process maually one by one ,but they are many.
how can i execute this , need your inputs.
thanks in advance
vamsi

Check that the scheduler is running in SMQR
Read,
http://help.sap.com/saphelp_nw04s/Helpdata/EN/e4/df5f3c8dde1c67e10000000a114084/content.htm
Regards
Juan

Output message of PO in ECC not processed automatically after order released in GTS

Dear Experts
PO created in cobalt was blocked in GTS due to legal control. output message of PO was blocked, after the PO was manually released by the user next day, AU open the PO and saved it. output message got processed.
Can you please let me know, why system is not processing the output automatically after the PO is released in GTS.
Is this the standard process?
Thanks
Kiran

Hi Kiran,
This is called follow on function in GTS.
When document is released, you could trigger background job regularly to process these document.
Open the area menu for SAP GRC Global Trade Services in your feeder system (with transaction code/SAPSLL/MENU_LEGALR3) and choose Recovery Follow-On Functions in Feeder System .
Choose one of the following entries to configure the follow-on functions for the selected application level: Materials Management Trigger Follow-On Functions for Purchasing Documents
Check more details in help document.
Trigging Follow-On Functions after Document Release in SAP GTS - System Administration - SAP Library
Best regards,
Vincent

In SMQ2 files are not processing automatically

Hi
I'm uploading the data using XI to ECC system. I'm facing a problem with a Q in ECC.
Each and every file when I upload it is getting stuck in ECC. So, I will have to go to SMQ2 in ECC and unlocking it and activating it and refreshing.
I also confirm that files will have only limited records like say 5 records with very minimum fields.
This should be done automatically why is this happening? Is there any Note to apply for the same.
Thanks.
C.

Generated Q and finished the issue.

Field BKPF-BVORG in idoc not processed

hi,
we are using idoc-type FIDCC2 for posting FI-documents.
In the idoc we have filled field BVORG. when the document is created BVORG is empty and not taken from the idoc.
does anybody have an idea ?
best regards, Martin

Correct. At least one BSEG-BUKRS (there could be multiple line items in BSEG) should be different from BKPF-BUKRS for the field BKPF-BVORG to have any value in it. When you post cross-company code document, you initiate the posting in one company code and system posts two accounting documents (assuming there are two company codes in question) - one in the initiating company code and another in the second company code in question. The value in BKPF-BVORG in the initiating company code document is the document number + initiating company code + last two digits of the fiscal year. The same value gets stored in BVORG of the header record of the second company code document as well. Please note that the BELNR in the second company code can be different from the BVORG, since that BELNR is determined from the number available in the number range of that second company code. In case of the first company code, the BELNR is same as the first 10 characters of BVORG.
The value in BVORG "links" the accounting documents in the two (or more) company codes involved in the cross-company code business transaction. There is no BVORG in BSEG.

Delete Idocs not processed

Hi, I know there are some Reports to execute which will delete Idocs. We have some Idocs that have status 51, and want to delete them.
Any ideas?

Hi,
1st way:-
IDOC Related programs
1. Archive RSEXARCA and RSEXARCB
2. Delete RSEXARCD 
3. Read archiveRSEXARCR
4. Restore RSEXARCL
2nd way:-
use FM EDI_DOCUMENT_DELETE .
pass the IDoc Number to it and delete the one which you want.
3rd way:-
use the tcode WE11 or program RSETESTD to delete an IDOC
Regards
Sudheer

FAGL_FC_VAL executed but the batch is not processed in SM35

Hi,
FAGL_FC_VAL executed but the batch is not processed in SM35 and I deleted this batch (Session).
My understanding is when we execute FAGL_FC_VAL only system valuate but posting happens only when we run the session in SM35. Am I correct ?
Or have I done mistake deleting this session in SM35?
Second time when I am executing FAGL_FC_VAL , no listing is generating. Please suggest what could be the reason for this?
Thank You

Hi,
This is how Batch Input Session Name field in foreign currency valuation works. If you happen to enter a batch input name, a batch session will be created and you would have to use transaction code SM35 to process it yourself. It will not process automatically. However, if you leave the the batch input session name field blank, and you check create postings, postings will be made immediately when you execute the transaction.
With regards to no listing generating the second time, make sure you check the Create Postings as suggested by the previous contributor.
Regards,
Elias

Condition-Dependent Output not processed

Hello,
I have configured conditions for output for purchase order documents (BUS2201) in the following path in SPRO > SAP Supplier Relationship Management > Cross-Application Basic Settings > Set Output Actions and Output Format > Condition-Dependent Document Output.
The purpose for this is to check the purchase order status prior to sending out the PO as to ensure that only successfully replicated POu2019s are sent to suppliers. When I create a PO that passes the conditions (iow the conditions are True), the output is generated in a Not Processed status. I have to now process the output manually or by running program RSPPFPROCESS. Once processed, output is successfully sent.
Note that the Time Of Processing setting is set as u201CProcessing when saving documentu201D. I would expect the output to be processed automatically by the system, but it is not.
If I create a purchase order that does not pass the condition (iow the conditions are false) an output is also generated with a Not Processed status, but I am unable to process it due to the conditions that are not met.
Please advise why the output that passes the condition is not processed automatically.
Kind Regards
Rene

Hi, If you want to work with Condition-Dependent PO Output, you have
to set the conditions for output in Define action for Purchase order
output. Under Action determination and Action summarization you can
choose from different option. Also clean-up customizing inconsistencies using transaction SPPFCADM and adjust to determination technology "Determination Using Conditions" to retest. Check note 564826 which may be helpful.
Best Regards
Lauren

IDOCS Error - Not getting processed automatically

Hi All,
We are loading hierarchy for a Product from R/3 system using the standard datasource.
When we execute the info package, IDOCs are not getting processed automatically.
We are facing the below error message.
Error when updating Idocs in Business Information Warehouse
Diagnosis
Errors have been reported in Business Information Warehouse during IDoc update:
No status record was passed to ALE by the applicat
System Response
Some IDocs have error status.
Procedure
Check the IDocs in Business Information Warehouse . You do this using the extraction monitor.
Error handling:
How you resolve the errors depends on the error message you get.
But when we goto BD87 and process the IDOCs manually, these are getting posted and the hierarchy is loading.
Can someone please guide me on what is the issue with the IDOCs and how to make them to post automatically.
Thanks in Advance
Regards,
Sachin

Hi,
This will happen due to Non-updated IDOCu2019s in the Source system i.e., occurs whenever LUWu2019s are not transferred from the source system to the destination system. If you look at RSMO of the status tab, the error message would appear like u201CtRFC Error in Source Systemu201D or u201CtRFC Error in Data Warehouseu201D or simply u201CtRFC Erroru201D depending on the system from where data is being extracted. Sometimes IDOC are also stuck on R/3 side as there were no processors available to process them. The solution for this Execute LUWu2019s manually. Go to the menu Environment -> Transact. RFC -> In the Source System from RSMO which will asks to login into the source system. The u201CStatus Textu201D for stucked LUWu2019s may be Transaction Recorded or Transaction waiting. Once you encounter this type of status Execute LUWu2019s manually using u201CF6u201D or Editexecute LUWu2019s(F6).Just keep on refreshing until you get the status u201CTransaction is executingu201D in the Production system. We can even see the stuck IDOCu2019c in Transaction BD87 also.Now the data will be pulled into the BW.
Hope it helps a lot.
Thanks and Regards,
Kamesham

ALE - Idoc not getting processed automatically, instead going fine in Debug

Hello All,
I have a problem with Inbound idoc processing.
IDoc settings were made 'immediate processing' in WE20, and the process code is set correctly and the attached of Z-Fun. module to process the idocs to process code.
The error in inbound side is as 'Function module not allowed: APPL_IDOC_INPUTI' 51 status. Am sure i have to do some thing with ALE settings.
Can some body help me with correction step or sequence of steps for this ALE process.
Thanks & Regards, Jilan

Hi Jilan,
Plz follow the steps:
ALE Configuration:
     WE30 - IDOC type creation
     WE31 - Create segment
     WE81 - Message type creation
     WE82 - Link IDOC type to Message type
     SE37   - Create Inbound Function Module
     BD51 - Maintain entry for Function Module
     WE57 - Maintain
     BD57 - Link Function Module, IDOC type and Message type
     WE42 Create Inbound Process Code
     BD67 - Link Process code to Function Module
     WE20 - Create Partner Profile
     BD64 - Display Distribution Model
     WE02 - IDoc List, Display all Inbound/Outbound IDocs
     WE14 - Outbound Processing of IDocs
     BD20 - Inbound Processing of IDocs
1st Step:   Create a Segment ( WE31)
         Segment is a structure for passing data in IDoc. It actually contains the IDoc data, just like the DDIC table/structure. Segment is created with all the required fields. Then Save it. But, to actually use this Segment, you have to Release the Segment, otherwise u cant use the Segment, by menu, EDIT--> Set Release.
         Now, if you want to do some change to this Segment, u cant, unless & until u Cancel the Release, by Edit--> Cancel Release.
2nd Step:   Create IDOC Type ( WE30 )
        After creating the Segment, now we have to create the IDoc Type. IDOC Type is like an envelop of a letter, which contains the data inside it, & also some more information like address. IDoc type can be Basic Or Extended.
       Basic IDoc Type: Using some SAP existing IDOC type (ex. MATMAS) or Custom IDOC type.
       Extension IDOC Type: When we need some fields extra to an existing IDOC type, then we can extend that Basic Idoc Type by another Segment. This is called Extended idoc type
3rd Step:   Create Message Type (WE81)
     Message Type is like the Postman for sending the Letter.
4th Step:   Attach Message Type to the IDOC Type (WE82)
5th Step:   Create a Function Module (SE37)
       Write the Processing logic in a Function Module.
6th Step:   Mention the IDOC Type, i.e, 0/1/2 (BD51)
7th Step:   Assign the Message Type, IDOC Type & Function Module (WE57)
8th Step:   Create a Custom Process Code (WE42)
9th Step:   Attach the Function Module to the Process Code (BD67)
10th Step: Execute Inbound IDOC s (WE19)
Example Function Module: IDOC_INPUT_ORDERS (Standard FM to create Sales Order).
reward is useful,
regards,
Tanmay

IDOC is not processing in R/3 with status 64(Urgent)--Production issue.

Dear Folks,
Here we are implementing MIRROR sytem for data extraction in to BIW.
I had gone through the steps in PDF file(How to minimize down thime for Delta Initialization) which has given by SAP.
These are following steps I had performed in BW production
1. Using RSADMIN transcation- Assigned one user as a Debugging user.
2. With the Debugging user Created one infopackage on Purhcasing ITM datasource--
 In data selection tab, I given date as from 2002 to 2003
 In Update tab, I selected update mode as Initialize Delta process- without data transfer and Uncheck Update Data in master system immediately
 In schedule tab I selected option Start Data load immediately then Start extraction.
3.Data was requested and It was intialized properly with green status 1 from 1 Records.
4. In details tab Request, Extraction, transfer(IDOC and TRFC), Processing everything in Green color.
5.As per document I have checked in R/3 for IDOC with status 64 using transaction BD87/WE05
Problem is that IDOC is not processing in R/3 system. for that IDOC I have checked in BW montior screen using the option IDOC list in Source sytem, here also it is not showing any IDOCs.
Please let me know why BW sytem is not sending any IDOCs to source sytem.Is there any settings I could have miss in BW aswell as in R/3 system.
Note: In BW production I successfully loaded master data from R/3. aswell as I triggered infopackage-Initialization with data transfer, it is showing IDOC number properly in R/3 system.
Points is Assured for all replies.

Hi,
- check you RFC destination (normal test + authorization test)
- Check you partner profiles in WE20 and its ports WE21
- from the source system tree (RSA13) right click your source system and perform a check
- the best is to restore your source R/3 source system from BW (right click on it ans select RESTORE); you'll need to be able to log in the source system as an admin as well as opening the source system for customizing in SCC4 so that BW can recreate the correct partner parameters automatically; the best is to do that with your basis group.
hope this helps,
Olivier.

IDocs in WEOUTQUEUE not processed

Hi all,
I have a problem with IDocs' serialization. I want to send IDocs of specific message types via IDoc outbound queue (trans. WEOUTQUEUE) .At sender system side in outbound partner profile (WE20) I configured IDoc to be send by Queue Processing with rule "constant:ediqueue". IDocs arrive to queue in WEOUTQUEUE, and here the problems begin:
1. Processed messages stay in queue - why?
2. If I send 1 IDoc it's not sended automatically, I have to activate queue in order to process it. It ried to use report RSEOUT00,but it only shows how many IDocs ready for processing and doesn't send them - how can I configure automatic processing of Idocs in queue?
3. If I send (with WE19) more then 1 IDoc at once, thay are automatically processed, but in XI in SXMB_MONI i see that they are processed by random QRFCs and are not serialized.
Can anyone please help me to work it out?
Thanks!
Anna.

We are having a similair issue. I have IDocs outbound from R/3 to XI. The Idocs are setup as "Queue Processing" with "Transfer IDoc Immed" option in the WE20 partner profile for EOIO processing. I usually have no problem all day long but every night right after midnight all the Idocs remain in a status 30. I have to use WEOUTQUEUE to activate the que or BD87 to release them. Once I do this, all IDocs moved along successfuly except every once in awhile during the middle of the day they go into a status 30 and remain there. I did notice the difference between the Idocs that work and the others that get stuck is the there are 2 entries for status 30 when viewing the IDocs in WE02. Here is what they look like. IS this simialiar to your issue?
03 - qRFC used to send IDoc to SAP system (I get this once I releaqse them manualy)
30 - blank
30 - Receiver exists , No filters , No conversion , No version change
01 - blank

Idoc in 53 status but not processed completely. Missing authorisation error

Hi ,
Some of the ORDER Idocs are in 53 status, but the orders are not processed successfully and no PO created for these Idocs.
They got below warning message when I checked in WPER transaction code.
" Missing authorization: Purchase Order Create Purchasing Grou 110 " - "Workitems (tasks) were created for this IDoc"
This is happening once in a while for some of the idocs. Remaining all idocs are posting successfully.
These IDOCu2019s are processed via user background. Not sure why we have authorisation issues as this user has SAPALL. Any ideas?
Thanks
Deepthi.

done.

J2EE process in SAPMMC do not start automatically after a restart

Hello All,
I have a Netweaver with only J2EE engine set up.
Whenever I restart the server, the services at SAPMMC->Console Root-> SAP Systems-> Instance-> Process List,Current Status, Open Alerts, J2EE Process Table do not start automatically.
I have to start them manually.
Please let me know what configuration I need to make them automatic.
Thanks
Raman

Hi,
Please confirm that J2ee is failing to start when you restart the server. If yes do post the logs so that we can drill to the max extent.
Rgds
Radhakrishna D S
Edited by: Radhakrishna D S on Sep 8, 2008 8:17 AM
Edited by: Radhakrishna D S on Sep 8, 2008 8:18 AM
Edited by: Radhakrishna D S on Sep 8, 2008 8:19 AM

CRS process does not startup automatically when the system is rebooted

Hi. all.
SOME TIMES(not always), CRS process ( exactly OracleCRService on
windows2003) does not startup automatically when the windows2003 is
rebooted.
O/S is windows2003 server.
DB is 10.2.0.2.0 RAC database that has 2 nodes.
I am testing a RAC database configuration, and thus rebooting one node
intentionally by turn.
I have tested about 20 times, and 17 times is OK. All required process is up
and all instance is up.
However, 3 times, OracleCRService services does not start, and concequently
database instance does not start automatically.
Here is the log of "crsd.log" file on the active node.
2007-05-31 17:43:13.281: [ CRSEVT][1720]32Processing RecoveryDone
2007-05-31 17:46:51.968: [ CRSRES][3876]32StopResource: setting CLI values
2007-05-31 17:46:52.437: [ OCRMAS][2368]th_rcfg_con: pudata retval [12]. Member [2] might have gone down
2007-05-31 17:46:52.437: [ OCRMAS][2368]proath_master: Node [2] came up/down 1/0 [1]. Problem retrieving pubdata. Should get down reconfig soon
2007-05-31 17:48:26.890: [ CRSCOMM][2852]32Retrying after CLSC timeout tonmsp109
2007-05-31 17:48:27.000: [ CRSCOMM][2852]32Retrying after CLSC timeout tonmsp109
2007-05-31 17:48:27.109: [ CRSCOMM][2852]32Retrying after CLSC timeout tonmsp109
2007-05-31 17:48:27.218: [ CRSCOMM][2852]32Retrying after CLSC timeout tonmsp109
2007-05-31 17:48:27.328: [ CRSCOMM][2852]32Retrying after CLSC timeout tonmsp109
2007-05-31 17:48:27.437: [ CRSCOMM][2852]32Retrying after CLSC timeout tonmsp109
2007-05-31 17:48:27.546: [ CRSCOMM][2852]32Retrying after CLSC timeout tonmsp109
2007-05-31 17:48:27.656: [ CRSCOMM][2852]32Retrying after CLSC timeout tonmsp109
2007-05-31 17:48:27.750: [ COMMCRS][2668]clsc_send_msg: (028BA8A0) NS err (12571, 12560), transport (533, 57, 0)
2007-05-31 17:48:27.750: [ CRSCOMM][2852]32CLSC connect failed tonmsp109ret = 9
2007-05-31 17:48:27.859: [ CRSEVT][2852]32invokepeer ret 200
2007-05-31 17:48:27.859: [ CRSRES][2852]32Remote start never sent to nmsp109: X_E2E_NotSent : Failed to connect to node: nmsp109
(File: caa_CmdRTI.cpp, line: 492
2007-05-31 17:48:27.859: [ CRSRES][2852][ALERT]32Remote start for `ora.nmsp109.gsd` failed on member `nmsp109`
Is there anyone who can help me?
Thanks in advance.
Best Regards.
Message was edited by:
user507290

oops- wrong forum!
Please try the RAC forum.

Idocs not processed automatically in BW

Similar Messages

Maybe you are looking for