Outbound TRFC IDOCS are strucking

Outbound TRFC IDOCS are strucking in our production system with the status : "Transaction recorded". When we are processing manually through SM58 they are moving.
Can any one help me to resolve this?
Thanks in advance...
Regards,
Nani.

Hi
Have you checked , is this the issue everytime or generally when some big load is running ?
generally this happens when the transaciton queue gets filled up quickly and if the instances of LUWs in that queue take long time to process.
Please have look at the load and try to reduce data volume that need to be processed in one LUW this will lead to low run time of the excution of LUWs and can reduce the hanging up of your LUWs from being processed.
hope it helps in some analysis
regards
Vishal

Similar Messages

Idocs are not received in Destination side.

Hi Friends,
I have a small doubt regarding SM58.
I have 2 dev systems.
client 100 & 200 we are send the Material data from 100 to 200.
In 100 system all are fine and the status is 12 and green but those are not received in 200.
When we check in 200 all the IDOCs are strucked in SM58(TRFC queue).
Please suggest me?
Regards,
Venkat.

Hi,
Please check the system RFC connection in WE21 and resend.
Regards,
Nandha

Outbound Idocs are not generated for some material number MATNR

Hi all,
We are using a custom program to process the IDOCS to some other thirdparty systems.
but the problem is the IDOCS are not generated and also we can't find the IDocs in TRFC also.
But it is working for the other matnr.
I have already debug the custom program, and it is taking all the inputs correctly.
plz guide me guys

Hi Praveen,
This is the code I am using
LOOP AT GS-MATNR_WERKS ASSIGNING <MATNR_WERKS>
GS-COUNT = GS-COUNT + 1.
    GS-TEXT = 'IDOC for Material & & (& of &) is just being created'(001).
    REPLACE '&' WITH <MATNR_WERKS>-MATNR INTO GS-TEXT.
    REPLACE '&' WITH <MATNR_WERKS>-WERKS INTO GS-TEXT.
    REPLACE '&' WITH GS-COUNT            INTO GS-TEXT.
    REPLACE '&' WITH GS-LINES            INTO GS-TEXT.
    CONDENSE GS-TEXT.
    CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'
         EXPORTING
              TEXT = GS-TEXT
validation code for the MATNR & WEKRS
CALL FUNCTION 'Z_MASTERIDOC_DISTRIB_ZCOPEBOM'
         EXPORTING
              MATNR        = <MATNR_WERKS>-MATNR
              WERKS        = <MATNR_WERKS>-WERKS
              MESSAGE_TYPE = P_MESTYP
GS-CREATED = GS-CREATED + 1.
    GS-COMMIT = GS-COMMIT + 1.
    IF GS-COMMIT >= 100.
      GS-COMMIT = 0.
      COMMIT WORK.
    ENDIF

Outbound Delivery IDOC not updating values from MKPF for goods receipt

hi all,
I have a question say I am generating an outbound delivery IDOC. which has fields Goods Issues & Goods Receipt date retrieve from MKPF(BUDAT).
say when i post goods issues, MKPF is updated and IDOC is gernerated with issues date taken from MKPF.
and when i tried to goods receipt, MKPf is updated and IDOC is generated but no receipt date taken from MKPF. then i check in MKPF, date is there and then once again I triggered the IDOC, receipt date comes......so my doubt is the time issues say when IDOC is triggeres, no value in MKPF...but when i check the time it is 4 mins difference from the MKPF time and the IDOC time...
and also 1 more thing for doing goods receipt, we do in different transaction and for good issue we do in Vl02n.
so bit confused.
kindly help

True , but in BKPF only Issues date are stored not the receipt date say if the document type = WE.
Please let me know is there any other options to fetch rather than MKPF.
because at the time of IDOC generation, there is not entries in MKPF. I tried to do using WAIT UP TO 50 seconds , even that didnt work.
Please guide me
thanks

How PO/Outbound delivery idoc can be triggered automatically once PO is created.

Hi All,
We have a requirement that we need to automate the process of generation of Purchase Order & Outbound Delivery Idocs as soon as they are created in using ME21N and VL02N standard tcodes.
Currently we are using ZDID Output type as craeted in NACE and below WE20 Message Control Entries:
For PO -
Application             EF : Purchase Order
Message Type:      ZDID : Direct Delivery PO
Process Code       ME10 : ORDERS: Purchase order
For OB -
Application        V2 : Shipping
Message Type:      ZLD0 : Delivery Note
Process Code       DELV : Delivery DELVRY01: DESADV/CARNOT/WHSORD/SHPORD
Also, BD64 entries are already maintained.
As per current process, we manually go to ME23N/VL02N tcode->and execute output type which generates Idoc in we02.
Can any one help me getting this automated urgently.
Thanks
neha verma

Hi Neha,
Use Change Pointers Concept for Both PO & Delivery Note.
So that, as soon as a Create/Change/Delete activities happen on PO & Delivery Note, IDOCS will be triggered automatically.
PO Change Pointers
http://scn.sap.com/docs/DOC-45107
Same setup for Delivery Note as well.
-santosh.

FM for outbound payment idoc

Hi,
How do we find out the FM for outbound payment idoc?.Here are the details
Message type-PAYEXT
Idoc type-PEXR2002
Thanks,

This thread is was last replied more than a year ago, but I'll add a little just to contribute.
WE60 documentation for the IDocs don't really give much except field / segment
information, but don't talk about where the fields come from.
FI_EDI_PAYEXT_PEXR2001_OUT seems to be the right FM, not sure how it relates to IDoc type pexr2002 as 2001 is the older version, but perhaps it handles the difference somewhere inside.
As to where certain segment fields come from (i.e. the mapping to master data fields...) , I've been debugging and still in progress.
I have not been able to find any straight forward mapping, and my comments at the moment are:
For any particular segment field of PEXR2002, take a look at FM :
FI_EDI_PAYEXT_PEXR2001_OUT
to see how it populates the field. Chances are, the values come from the tables REGUH/REGUP/REGUV.
The payment run process as far as my knowledge is concerned is as follows:
1) Payroll Run -> Stores to table BT
2) Pre DME (e.g. trx PC00_M08_CDTA) picks data frm BT and creates payment data in REGUH / REGUP / and REGUV tables. This gives you an identification feature ID for the next step.
3) RFFOEDI2 changes status field in REGUH for particular payment data record based on ID from step 2.. this enables it to be picked up in the next step.
4) RFFOEDI1 converts the record in REGUH into an IDoc which can be processed in BD87.
I have debugged from step 4 backwards to step 3, i.e. I know that segment field X comes from REGUH field Y. Now I have to debug step 2 to find out how it populates REGUH field Y. If this comes directly from master data, then that makes life easier. But if this REGUH field Y comes from table BT of step 1, then perhaps I have to debug the payroll run somewhere. (Nightmare?
Anyway, if anyone knows better, please advise.

Idoc are posting to ECC with Status 64

Hi All,
We are receiving IDOC with status 64 from PI.
We used tried by changing the options in partner profiles
--> Trigger by Background program
The inbound IDoc is processed in the background. In this case, make sure, that the report RBDAPP01 is scheduled in the transaction SM37 as a regular job with the correct variant to process all IDoc´s, which have this processing option maintained.
--> Trigger immediately
When using this setting, it is important to have sufficient resources for the immediate processing of the inbound IDoc´s. One dialog work process must be available for every single IDoc.
If this dialog work process is not available, the IDoc cannot be processed and stays in status 64.
I reffered the notes
555229 ‘IDocs hang in status 64 for tRFC with immediate processing’
734576 ‘IDocs retain status 64, but should be processed immediately’
1055679 ‘IDoc-tRFC inbound with immediate processing may not work’
Still the idocs are in 64 status, every time im re-processing them manually. even after re-processing some of them are going to 51 or 54.
Please help me.
Regards
Bhargava Krishna

Hello,
Can you please explain your issue is with "Trigger by Background program" or "Trigger immediately"?
For Trigger immediately, if there is no free dialog work process available than IDocs are posted with status 64.
For Trigger by Background program, Background job RBDAPP01 will process IDocs depending on variant you define to select & process IDocs(i.e., IDoc Status = 64).
It is always recommended to use "Trigger by Background program" for high volume interface which has large number of IDocs.
Help on RBDAPP01
Regards,
Sameer

Multiple ALEAUD Idocs are being generated per original Idoc

We have the following scenario in PI:
ERP (IDOC)> PI (JDBC)> 3rd Party
PI sends ALEAUD idocs back to ERP when the process is successful. Program RBDAPP01 is then ran on a schedule to update the ALEAUD idoc status, which in turn, updates the idoc status of the orignal idoc sent from ERP (03 to 12).
We just upgraded our PI from 7.0 to 7.1. Now, it seems multiple ALEAUD idocs are being created for each ERP outbound idoc. It used to be 1-to-1. From what I can tell, it look like an ALEAUD it created for every receiver. For example, if we sent one idoc and the data goes to 3 receivers, 3 ALEAUD idocs are created. This causes an issue because the first ALEAUD idoc will update the original outbound idoc to status 12, but any other ones will take it from status 12 to status 09. We want it to stay in status 12.
Any ideas why 7.1 would be any different?

This seems to be the standard behavior. I will explain it.
If an idoc comes and message is sent to say three receivers, all the three message should generate the ack unless they are not disabled. And in this case you will find multiple ALEAUD message at sender. In case the receiver adapters are like File, JDBC which do not support application ack, then ALEAUD won't be sent and you will receiver "Applicaition Ack Not Supported". With this error, if multiple ack are seen in sender then I guess they won't actually perform any update.
Regards,
Prateek

Outbound error IDoc reprocessing

I have a scenario like whenever an outbound idoc is in error status, should be able to correct the idoc n reprocess it.
Suppose outbound idoc is in status 02. System process code will notify the agent assigned in partner profile. When i execute the workitem and corrected the port and try to reprocess, this status is set to 30. My requirement is once i correct the port status should become 03. How do we acheive this ? (not through report rseout00 )
1. In general scenario how do we handle outbound error idocs?
2. Is system process codes are used only for notifications or error processing?
Inputs will be appreciated regd outbound error reprocessing .
Thanks.

Hi Indira,
1. In general scenario how do we handle outbound error idocs?
You can use transaction BD87 to monitor the IDoc statuses.
and use the following programs to reprocess outbound and inbound error IDoc(s).
RBDAGAI2 - Re-processing of IDocs after ALE Input Error
RBDAGAIE - Reprocessing of Edited IDocs
RBDAGAIN - Process Outbound IDocs with Errors Again
RBDAGAIP - New Posting of Partially Posted IDocs
RBDMANI2 - Manual Processing of IDocs: Post IDocs Not Yet Posted
RBDINPUT
2. Is system process codes are used only for notifications or error processing?
The process code ise used in both ALE and EDI framework to identify the function module or API (Application Programming Interface) to be invoked for subsequent processing. Inbound as well as outbound interfaces use process code but for different purposes. Outbound process codes are stored in table TEDE1, while inbound process codes are stored in TEDE2.
Hoep this will help.
Regards,
Ferry Lianto

Split outbound ORDERS idoc to different ports

Hi All,
I was wondering whether it is possible to split an outbound ORDERS idoc and have it directed to two different ports based on document type? Client requires normal PO's to be written to one XML while STO's be written to a seperate file. Look forward to your responses.
Regards,
John

Hi,
These are the exits available for Outbound ORDERS idoc.
1. ORDERS Purchase order / order MM06E001 EXIT_SAPLEINM_001 Customer enhancements
for control
record: purchasing
document, outbound
2. ORDERS Purchase order / order MM06E001 EXIT_SAPLEINM_002 Customer enhancements
to data segments,
purchasing
document, outbound
3.ORDERS Purchase order / order MM06E001 EXIT_SAPLEINM_011 Final customer enhancement
EDI purchase
order outbound
You should create the project before implementing the exits. So that the break point is going to stop over there.
Check this link to know how to find BADI -
http://www.sap-img.com/abap/how-to-find-bapi-for-particular-transaction-in-sap.htm
In your case this BADI is there for the given program.

Confirmation IDOCS are stuck with BBP_CO_WE

Hi experts,
We are building SRM 7 with ECS. We are connected to ECC 6 EHP4.
When we create CF, IDOC is not transmitted to backend.
In RZ20 we have those logs :
Backend goods receipt errors | Status attribute | BBP_CO_WE
In ECC inbound IDOCS are not there
It seems the problem is related to ECC config.
Any idea to be able to send IDOC?
Many thanks in advance.

Hello,
So, your IDoc is not in error.
Check the 'Outbound Options' tab for message type MBGMCR of R/3 backend Partner Type in WE20 transaction.
In frame dedicated for 'Output Mode', radio-button "Transfer IDoc Immed." should be selected.
Execute same check for message type SYNCH.
Regards.
Laurent.

CRMXIF_PRODUCT_INDOBJ outbound Bdoc / Idoc

Hi All,
I'd like to use the PRODUCT_INDOBJ BDOC and the resulting CRMXIF_PRODUCT_INDOBJ_SAVE01 IDOC to transfer some data to an external system. The BDOC and IDOC are correctly generated when I change the IBase components. I'd like to add some additional fields into the IDOC which are not in the BDOC.
In the past, I have implemented the relevant BADI provided by the XIF framework - i.e. for service orders I've implemented the CRMXIF_ORDER_MAP badi and this works fine.
I've tried implementing the CRMXIF_PROD_IO_MAP badi but the code doesn't seem to get called. I've tried putting a breakpoint in the implementation and a large wait statement. The BADI doesn't seem to get called. I have activated the implementation.
Any idea why the CRMXIF_PROD_IO_MAP Badi is not being triggered between the BDoc and IDOC generation?
I've put my code in the CHANGE_MAPPED_DATA_OUT method as this is an outbound interface.
Cheers
Richard

Hi,
Do you have any guide of how to Enhance a BDOC and Create Mapping With the IDOC to send it to an External System through XIF.
I'd appreciate any info.
Thanx in advanced
josemcu-at-/gmail=dot=com

Outbound 855 IDoc Creation

Hi EDI Experts,
I have a requirement.
I want to send my outbound 855 IDocs out of SAP. But there is some twist here.
I cannot send my Outbound IDocs as soon as the Sales order is created. Once the sales order is created, at a later point of time an acknowledgement code will be added to the sales order. Only then I am supposed to send the IDocs out of SAP. (Infact IDocs should be created at that point of time). either batch or not is fine.
Any idea/suggestion how this can be achieved.
Ur comments are most valuable and welcome.
Thanks,
Matt

Thanks MxG for the Reply.
But I am just wondering what kind of output requirement i can use in this scenario.
2 - Order Completion.
Steps:
1.Inbound 850 IDoc comes into SAP and Creates an Order.
2. Outbound IDoc will be created (If Req is set to 2). But I don't want IDoc creation @ this point.
3. Order will be updated by an acknowledgement code by CR.
4. I need IDoc creation @ this point of time.
I am not seeing any Output Requirement that satisfy this condition.
What should I do??
Thanks Agai and waiting 4 ur reply
Matt
Edited by: Creasy Matthew on Jul 24, 2009 1:22 AM

Sales Order - Outbound Delivery IDoc scenario.

Hi Friends,
I have the below urgent requirement. I would be gratful, if someone suggest possible options.
Scenario: This is related to Sales order to Billing scenario.
We are creating Sales orders by using ORDERS05 Idoc. After the Real goods despatch happens at legacy system, we will be getting despatch feed (IDoc) for outbound delivery trigger. Here if all sales Order items are complete, the system is creating Outbound delivery by using this IDoc and then PGI will follow. This is Ideal scenario.
Practically what happening is, our sales orders are created with few incomplete items (Ex: Net price missing) because they are created via ORDERS05 Idoc.( Manually, we can't create sales order with incomplete items, unless we force the system to do so). When the Out bound delivery IDoc triggered, it will pick up only completed items and creates partial delivery and becomes 53 status. Now the sales order is left out with open and incomplete items.
Now our aim is how to make this outbound delivery IDoc fail, if this is not able to create delivery for all items?? (I mean, if the sales order items are incomplete, the delivery Idoc must fail. So later, if sales order becomes complete, this Idoc can be reprocessed again) How can we make this scenario possible??
Expecting your thoughts and inputs.
Regards,
Kaleeswaran

HI,
I suggest you to think of similar solution as below.
1.As your issue is at order (few items are incomplete with Pricing issue or some other issue), at sales order level while saving each sales order write the code in user exit_save_document_prepare to check if any items exists as incomplete. if yes then populate a delivery block in the sales document header.(you can use a new delivery block to distinguish the reason for the block)
2. While creating delivery for the order through Idoc since the incomplete orders have a delivery block at the sales document header level SAP wont create delivery for the entire Order.
3.Handling this delivery block at sales order header: when ever a sales order is popluated with this new delivery block triggere a workflow which will shoot a mail to your End user team or customer representative team. they will correct the issue in the order and remove the delivery block. if you dont want to go with a workflow then you need to incorporate a process to remove the delivery block in the sales order
Thanks,
Srini

How to suppress certain fields in ALE Outbound INFREC IDOCs?

Dear All
Is it possible to suppress certain fields in Outbound ALE IDOCs (for example INFREC IDOCs) ?
I am in need to send Info Records from one ECC system to another. The problem is, in the sending ECC system the INFREC IDOCs are created with the field E1EINAM-INFNR which carries the Info Record number. But the target ECC system might have a different Info Record already existing (for a different article) with the same Info Record Number. If the INFREC IDOCs are created without the INFNR field (i.e. if the field is blank) and then sent to the target system via ALE, it is successfully processed in the target system and a new Info Record is created with a different Info Record number. This is what is required. How can it be made possible?
Thanks
Vignesh Sankaranarayanan

Use the transactions BD62, BD79 and BD55 to setup and assign conversion rules for your IDOC fields and set a constant '/' for the infnr field.
Test if that is enough or you might need to take extra care for the name field of info record texts. I am not in a system currently, so I can't check whether long text name is based on info record number or only a mix of info record keyfields (without info record number itself).
You should also have a look into my blog Stumbling blocks in purchasing info record migration by LSMW IDOC method
You will probably hit the one or other issue that I described too.

Outbound TRFC IDOCS are strucking

Similar Messages

Maybe you are looking for