Idoc issue - 3 idocs are generated

Moved to correct forum by moderator
hi
i am using USERCLONE message type to generate idoc for user releted data.
whenever i create new user, it generate 3 idoc for USERCLONE message type.
and only one has data.
therefore my question is can i generate only one idoc for USERCLONE message type instead of 3 idoc?
thanx in adv
manoj
Edited by: Matt on Nov 19, 2008 10:48 AM

HI ALL
THANX FOR THE REPLY
I AM USING TRANSACTION SU01 AND CHANGING THE USER DATA AND THIS TRIGGER OUR IDOC DUE TO STANDALONE CONFIG.
THEN I CHECK THAT IN WE05, HERE I SEE 3 IDOC AFTER I CHANGE ANY USER DATA AND ONLY ONE IDOC HAS DATA AND REST OF THE 2 IDOC DO NOT HAVE DATA.
SO IS IT POSSIBLE TO GENERATE ONLY ONE IDOC IN THIS CASE.
THANX IN ADV
MANOJ

Similar Messages

In DOM (or EOM) scenario, no IDOC is generated for XIF_IDOC site type

Hi friends,
I have a problem with an XIF_IDOC site in the Distributed Order Management (DOM).
We are using DOM scenario to separate and distribute CRM sales order
items to different sites. Under the tcode SMOEAC, I defined a new site
called "EKSIRLANDA" whose type is external interface for IDOC
(XIF_IDOC). I made a subscription of "DOM items" (DOM Order Split
(MESG) ) for the EKSIRLANDA site. After that, (under the tcode WE20) i
defined EKSIRLANDA logical system partner profile with the outbound
message type "CRMXIF_ORDER_SAVE_M". I saved a new order under the tcode
CRMD_BUS2000115, but no IDOC generated. After checking all the related
customizing and the CRM_DOM_ITEM_DISPATCH method implementation of
CRM_DATAEXCHG_BADI everything seemed all right. By the way, we are
using CRM_DATAEXCHG_BADI badi to separate the related items to the
related sites. Anyway, i added another subscription called "All
Business Transactions (MESG)" to the EKSIRLANDA site and saw that 2
IDOCs are generated. I investigated those 2 IDOCs. One of them is what
i want. In other words, it contains only the related order items that
are separated from the others in the CRM_DATAEXCHG_BADI
(CRM_DOM_ITEM_DISPATCH method). The other IDOC contains all the order
items. I do not want this second IDOC. If i remove "All Business
Transactions (MESG)" subscription and leave the "(DOM Order Split
(MESG)" subscription alone, no IDOC is generated. This is the problem.
Why does not "DOM Items" subscription alone generate any IDOCs? IDOC
settings are not wrong because when i add "All Business Transactions
(MESG)" subscription to the EKSIRLANDA (XIF_IDOC) site, the IDOC is
generated, but this time an extra IDOC containing all the items is also
generated. What is the problem?
Thanks in advance for your help.
Mehmet Karasu

nobody has no idea for this question ???

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 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

IDOCs not generating with classic scenario

Hi,
We are with SRM 7 with Classic Scenario.
Issue : SRM Org. structure is replicated from ECC system through IDOCS. But, suddently, no IDOCs are getting generated in SRM after we run PFAL in ECC.
IDOC is getting created in ECC after we run PFAL but not creating in SRM.
Your inputs are appreciated.
Thanks
Nag

Hi,
We have faced same issue.
You first check with tcode WE05 in both SRM & ECC. You will get to know which idocs present (transferred).
You can process unexecuted idocs using tcode BD87.
After processing idocs you must run distribution model.
This way we resolved our issue.
Regards,

IDocs are not transfering to XI

Hi,
When we create Shopping cart, in the back PO will create and it woould convert to IDoc and send to XI. But PO's are creating, IDocs are not reaching to XI, please let me know what would be the issue.
Thanks

HI,
Try this URL , i hope it will help u ,
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c09b775e-e56e-2910-1187-d8eba09c7a4a?quicklink=index&overridelayout=true
Regards,
S.Saravana

ALE VA01 IDOCs are sent two times ?

My ALE is working well, but for eacher sales order created, Two Idocs are send (Two different idoc number but the same sales order)!
I use message controle and a partner profile Ku ans LS.
So where can I check where is this double ?
Transaction ? Tables ? Spro?
Best regards
Henri

Hi Henri,
Why do you need to have two partner profile KU and LS?
Unless you want to send to different target systems. For example, KU is for customer 'ABC' and LS for CRM system.
If you need only to send one target system then use only partner profile and delete the other one.
Please ensure the two IDoc generated are having two different recipient (KU and LS) in IDoc control.
If both IDocs have same recipient then you may need to check the ALE and IDoc configuration again.
Please check NAST table for initial investigation.
Hope this will help.
and don't forget to reward points if helpful as a way to say thanks.
Regards,
Ferry Lianto

Message processed successfully in PI but IDOC not generated.

Hi,
Currenlty for some messages, Idocs are not getting genrated and
outbound queue in moni for this messages shows as IENGINE instead of
IDOC. Also the outbound flag doesn't have any status and there is no error information.
We are using message packaging but Before upgrading support pack from SP15 to SP21
we didn't face any issue regarding packaging.
Please suggest resolution for this if anyone have faced this kind of issue.
Thanks,
VK

Hi,
Please check what Markus said.
Also look for these settings in your scenario:
Check trace message in the SXMB_MONI ,
Check all queues are registered ? go to SXMB_ADM and check out this
Check about Receiver determination and Receiver Business Service is pointing to correct R/3 system. For this look into Adapter Specific Message Identifiers for the Reciever Business Service
If you are using BPM here ? If so check the BPM status
Let us know if this helps!
Divyesh Vasani

Several idocs got generated for the PO transmission

Hi,
We have got a problem regarding the transmission of PO via email or idocs. While PO generates only one output type with NEU. there are several idocs and email (depending on the condition record for the vendor and purchasing organization) getting generated and are dispatched to the vendor. There should be only one idoc or email generated for the PO dispatching to vendor.
Did anyone of us get this problem in the past? Please share your experience with me and if you have any solution for the same.
Best regards,
Subhash

Hi BK,
Thanks for your answer but there is just one condition record for this vendor. The problem is that, there is only one successfully processed message type 'NEU" in the purchase order but multiple idocs or emails are generated within a timespan of few seconds/minutes. These multiple records can be seen is SOST list (in case of email) and WE02 (in case of idocs).
Thanks n BR,
Subhash

F110-idoc-not-generated-rffoedi1

hi expert,
I am running a payment program F110 and the IDOC is not getting genrated for
the payment program. In the payment log i see the infomation
IDOcs were generated for the following entries.... but when i chekc the idoc by we05 i can't find any idoc,
please advice on it.
thansk

Hi,
Idoc's are generated based on the payment method and any how in the payment method we will give the required curriencies which are applicable for that payment method.
And u had mentioned as WE05 for IDOC list, but actually the T.Code for IDOC list is WE02.
Check the settings, it has to come. Reply back for more clarifications.
regards
srikanth.

EREC: Multipal IDOC are getting created in receiver system for one IDOC

Hello Experts,
I ran in to one wearied issue in IDOC creation in Receiver system. I am running PFAL in sender system for only Person but 10 IDOC are getting created in receiver system. I don't know why is this happening.
This issue started popping up after we ran RBDAPP01-Inbound Processing of IDocs Ready for Transfer. We ran this to change IDOC to 53 status. Now I don't know what went wrong but Perner distribution is behaving
Appreciate your help.
Regards,
Krishna Bidwai
Losangeles USA.
818 527 0204.

Yes, employee is getting created after adding 0003 into the filter, but can u please answer my another question, i.e. PERNR in sender and receiver system should be same.
So in Receiver system (ECC) do i need to maintain external number range for PERNR?
Thanks

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

Idocs are unable to transfer from R3 to PI system, IDOC status is 03

Hello Gurus,
Idocs are unable to transfer from R3 to PI system, IDOC status is 03
in sm58 getting below error
RFC are working fine
"EDISDEF: Port SAPCEP segment defn Z2SH_DESCR000 in IDoc type MATMAS03 CIM"
Regrds
vamsi

Hi,
I am also facing same problem, Can any one suggest me what is the issue..

Inbound Idocs are not Processing

Hi,
Inbound IDOCS queue is not processing if any one IDOC is showing amber(error) . Please let me know the resolution to avoid this issue or let me know the BASIS setting to avoid it.
Regards,
PVK.

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

Vendor IDOCs are not uploading in LFA1 table

Hi All,
We have a SAP system where Vendor IDOCS are coming from MDM through SAP PI middleware. The problem we are facing is we are not able to see all Vendors in LFA1 table.
In WE05 IDOCS are posting successfully but when we check for respective vendors in LFA1 table only few vendors are available there.
Can anybody guide us to solve this issue? Also pls let us know the process of uploading master data into table as we are very new in ABAP.
Regards,
Sarita

be open minded. SAP gives several import methods to load vendors. one of them is per IDOC.
But the vendor master IDOC does not automatically create the adress master.
And even more important, if you migrate data from one SAP system to another, the IDOC method is more straight forward than the batch input, because you can send the IDOCs from legacy system to new system, you will then have a 1:1 relation of the structure in LSMW and you can create vendor masters by knowing the new vendor number from an internal number range already in LSMW, long before you actually post the vendor. With batch input you can either post with numbers from external number range, or you just dont know the new number already in LSMW.
And you dont need to download the data to Excel. And further, the LFA1 adress data has less information than the ADRC adress data.

Idoc issue - 3 idocs are generated

Similar Messages

Maybe you are looking for