PI message packets effecting idoc events

Hello experts.
I seem to have a problem with message packets.
I receive several messages of type ALEAUD (not as acks, but as a regular IDOC), and when I send them to my
SAP ECC system they are being sent as a packet.
When an ALEAUD is being processed I want it to raise an event, however, an event is being raised for a packet only.
I asked SAP, and they told me that I can change AUD1 and there I can make it to raise an event for each IDOC
(but they will not support it, so I made a new process code named ZAUD1)
However when I send several IDOCS, there are 2 events that are being raised for the same IDOC, and an IDOC that has no event.
Can anyone please help?
How can I make every IDOC processing raise an event for that IDOC only?

Hi,
Trigger an idoc using we19 and set break points in your process code and debug to find out how the events are getting triggered...
need an abap knowledge on this take help of abaper if you are not..
HTH
Rajesh

Similar Messages

Prioritized Messages in combination with Event-Driven Message Processing

Hi,
our Scenario (EO): Sender A sends large IDocs to Receivers X and Y (> Split)
1.
What we did first:
Prioritized Message Processing
Sender A sends large Messages, therefore we prioritzied Messages in the IE with EO_MSG_SIZE_LIMIT > 4000.
This works fine: Messages are queued in XBTL and XBTM and afterwards they are send to Receiver X and Y.
2.
What we did next:
Event-Driven Message Processing
Now we want to send the Message from Sender A to Receiver X directly and to Receiver Y at night time.
We add Event-Driven Message Processing, Sender- and ReceiverID for A and Y,Job and so on...
On it's own (without Prioritized Message Processing), this works fine: The messages are send at night time.
But in combination (Event-Driven + Prioritized Message Processing) the messages only passes the Prioritized Message Processing and the Event-Driven is ignored.
Our "Hop-List" for Split A to Y was:
1. XBTL
2. XBTJ2008...
3. XBTM
But actually all Messages passes:
1.XBTL
2.XBTM
Why are the messages not filtered for the Event-Driven Message Processing (in combination with the Prioritized Message Processing)?

It was an error in the SourceCode and is now corrected by SAP:
Hinweis 1295746 - XI Runtime: Fehler in Ereignisgesteuerte Messageverarbeitung
Olaf

Can we show information messages after triggring IDOC's in background

Hi friends,
Iam executing one custom transaction for sales cycle in background, in that iam trigging IDOC's, user are getting the messages like
1. Idoc No: 0000014254 despatched to client -
2. 1Output were processed.
3. 1 IDOC's selected.
user has to enter 3 times while the transaction is running in background.
But requirement is "can i set all 3 information messages after trigging IDOC's to background.
any body suggest the solution.
regards,
vamsy krishna.

Nope nope, I don't work for Apple - I'm just a Level 3 Discussions pleb...! ;-))
I'd been in touch with the senior tiers of Apple Support on the phone to diagnose the chkdsk incidents of 2004-2005.
Following that, I also negotiated (part-)resolution to the Smart Playlist issue.
Since Updater 2006-01-10 (part-)fixed the Smart Playlist problem, but seemed to introduce some other issues for folks, I've been continuing to pass feedback from my Level 2 contact who is handling investigation of the latest problems. In turn, he is working with US Engineering to handle this issue.
So no, I'm not Apple, but I (and some others) pass commentary to and fro between Discussions and Level 2 Support, and by by-passing Front Line phone support, it helps us to get serious issues investigated and resolved more quickly. I find that such an approach for serious problems works well to help the Community.
I'm not sure if my message gives hope - but I do hope that having reported this on up to Level 2, and having been told that US Engineering have teams watching Discussions, that maybe we can expect some attention from Apple R&D on this matter. However, the official line is for individuals to contact Apple directly themselves via the phone and website feedback, so US Engineering have an idea of the number of people affected. The more people who report to Apple directly, the more likely the problem is to be noticed, and hence the priority for investigation and resolution increases. I can start an unofficial ball rolling, as I have done, but we cannot keep the momentum up unless users use these official routes to let Apple know they are affected.
Sorry it's all a bit foggy, but it's the best I've got! Hope this little explanation helps to clarify things a bit more. Feel free to post back if you'd like to discuss this further. Best for now.
Kind regards,
Gopha.

What is inbound XML message type and idoc type in Purchase Order response

Hi ,
We are on SRM 7 ECS , support pack SAPKIBKV08.
We have a process in which vendor will send a Purchase Order response which will be
converted to XML format by a middleware. This XML message will come to
SRM and post a POR. I want to do the EDI mapping for this XML message,
but there is no message type and idoc type in SRM for Purchase Order
response. How do I map my message type in SRM to the vendor sent fields
in middleware .
Please advise
Rgds
Sumendra

Hi,
You can process with XML without IDoc.
Vendor-> (XML) -> PI -> (XML) -> SRM.
Please check PurchaseOrderConfirmation_In in namespace "http://sap.com/xi/SRM/Procurement/Global".
http://esworkplace.sap.com
Regards,
Masa

How to get rid of messages in idx5 idoc adapter

We are having a lot of messages in idx5 (327828 for a particular date). When I go to sxmb_moni "Monitor for processed xml Messages" I do not find these messages there.
We are running the archiving/deletion reports and I expected theese to take care of the Idoc Adapter messages as well. Is this not the case? Are there separate archiving/deletion jobs for the idoc adapter? How do I get rid of the messages in the idx5 xml messages in the idoc adapter?
When running the report RSXMB_SHOW_STATUS this is today (after archiving/deleting all messages older then one day) showing good 30.000 messages in the database - and do not show the huge number of messages in the idoc adapter.

The baseball is probably the symbol assigned to you in Address Book - take a look and see. It appears on all your sent mail in Mail, but not on the messages as they appear to recipients, so don't worry about it too much. If you don't like it, you can remove or replace it through Address Book.

How to do message mapping in IDoc or RFC to file transfer ?

Hello guys. I have a doubt. I know how to do an IDoc to file or RFC to file scenario. But how to do mapping in an Idoc to file or RFC to file scenario ? As I understand mapping is done in the sender. But IDoc or RFhas no interface as its used for SAP. So where do we need to perform mapping ?

Hi,
You dont need the Data type and message type for IDOC's, RFC's and for external definitions. so u just create one DT,MT for your File structure and you need 2 message interfaces, one for file and one for the Idoc/RFC. You can use them in your mapping program.
Regards,
Kumar.
P.S: Reward Points if Helpful!!!!!!!!!

Problem with PSE9 - Receiving message window - CAHeadless Debuger Event.

In my last request for Technical support (Case # : 0181931685), I have 2 problems. One about inability to remove PSE9 and reinstalling was corrected by following instructions from Tech.Support. The second problem is still with me. The message window CAHeadless Debuger Event is poping up with the message ...\...\Src\DataManager.cpp-410. The window is having one button <Continue>. When I press the Continue button, everithing work and look OK until next time the windows pop-ups. The computer is new Dell Studio 8100 running OS Windows 7 Home Premium 64. Originaly I started using PSE9 on old Dell with Windows 7 Home premium 32 without any problem. Any advice how to stop this un-plessant message comming?
Thanks a lot! George.

Hi all,
this case is closed it was catalog issue. I corrected this by creating new catalog and importing pictures from hard drive. All is now correct.
George

Titles are not visible, they show up on timeline as a grey box no text does not effect other events or projects

titles are not visible, they show up on timeline as a grey box no text does not effect other events or projects. could this have something to do with motion

Without seeing the timeline it sounds as if they've been off. Maybe you pressed the V or the role is switched off in the timeline index.

Message types and idoc types

hi,
     i need the list of message types and idoc types for edi.
      can any one of u pls send it.

Hi,
Check the OSS notes 104606.
The following list maps the logical messages and IDoc types to the corresponding ANSI X12 transaction sets.That is, the logical message can be copied to the transaction sets named.
204 Motor carrier shipment information
           The logical message is SHPMNT or IFTMIN, the IDoc type SHPMNT03.
214 Transportation carrier shipment status message
           The logical message is TRXSTA, the IDoc type TRXSTA01. Inbound processing is supported.
304 Shipping instructions
           The logical message is SHPMNT or IFTMIN, the IDoc type SHPMNT03.
810 Invoice or billing document (also 880)
           The logical message is INVOIC, the IDoc type INVOIC01.
812 Credit and debit advice
           The logical messages are CREADV or DEBADV, the IDoc types PEXR2001 and PEXR2002.
820 Payment order and credit advice
           For the payment order, the logical message is PAYEXT (REMADV), the IDoc types PEXR2001 and PEXR2002.
           For the credit advice (ERS - Evaluated Receipt Settlement), the logical message is GSVERF, the IDoc type GSVERF01.
823 Lockbox
           The logical message is LOCKBX, the IDoc type FINSTA01. Inbound processing is supported.
830 Delivery schedule (LAB)
           The logic message is DELINS (from the EDI standard ODETTE) or DELFOR the IDOC type DELFOR01.
832 Price catalog (also 879, 888, 889)
           The logical message is PRICAT, the IDoc type PRICAT01. Outbound processing is supported.
834 Benefit enrollment and maintenance
           The logical message is BENREP, the IDoc type BENEFIT1. Outbound processing is supported.
840 Request
           The logical message is REQOTE, the IDoc types ORDERS01 to ORDERS04.
843 Quotation
           The logical message is QUOTES, the IDoc types ORDERS01 to ORDERS04.Outbound processing is supported.
850 Purchase order or order (also 875)
           The logical message is ORDERS, the IDoc types ORDERS01 to ORDERS04.
852 Stock and sale data
           The logical message is PROACT, the IDoc type PROACT01.
855 Order confirmation (also 865)
           The logical message is ORDRSP, the IDoc types ORDERS01 to ORDERS04.
856 Transport and shipping notification (ASN - Advanced Ship Notification)
           For transport in the SAP application, the logical message is SHPMNT or SHPADV, the IDoc types SHPMNT01 to SHPMNT03.
           For the delivery in the SAP application, the logic message is DESADV, the IDoc types DESADV01 (to be discontinued), DELVRY01 and DELVRY02.
860 Ordering modification (also 876)
           The logical message is ORDCHG, the IDoc types ORDERS01 to ORDERS04.
861 Credit advice (ERS - Evaluated Receipt Settlement)
           The logical message is GSVERF, the IDoc type GSVERF01.
862 Delivery schedule (FAB)
           The logic message is DELINS (from the EDI standard ODETTE) or DELJIT, the IDOC type DELFOR01.
864 Text message
           The logical message is TXTRAW, the IDoc type TXTRAW01. Inbound processing is supported.
940 Shipping order and stock order
           The logical message is SHPORD or WHSORD, the IDOC type DELVRY01.
945 Shipping confirmation and stock confirmation
           The logical message is SHPCON or WHSCON, the IDoc type DELVRY01.
997 Functional acknowledgment
           This is a technical confirmation. This is not exchanged via an individual message but the status report for IDoc processing. The status values used are:
           "22" Shipping OK, acknowledgment has yet to come
           "16" Functional acknowledgment positive
           "17" Functional acknowledgment negative
           The status values "14" and "15" are available for the Interchange Acknowledgment accordingly. Source code corrections
Cheers
VJ

The XI does not send messages with correct IDOC structure

SAP XI 3.0 sends to ECC IDOC HRMD_A07
The XI does not send messages with correct IDOC structure.
In XI Design, Software Component RHEVOLU, Ive imported the Objects
HRMD_A.HRMD_A07 from SAP ECC; In Tools -> Export Reduced XSD, I saved
HRMD_A.HRMD_A07.xsd in Namespace http://suezambiental.com.br/HR . At
Message Mapping -> mmAdmissao, in Imported Message -> Import XML or
XSD, I imported the reduced Idoc file generated above, mapping source
fields to target fields.
The IDOC sent from XI to ECC has this structure (template: 22122)
E1PLOGI
E1PORIG
E1PITYP
E1P0000
E1P0001
E1P0002
Status 53 -HR: ALE inbound processing for HR master data
But does not update HR Master data.
The structure expected in ECC side (template: 20376) is:
E1PLOGI
E1PORIG
E1PITYP
E1P0000
E1PITYP
E1P0001
E1PITYP
E1P0002
Status 53 -HR: ALE inbound processing for HR master data
By using WE19 transaction, this structure was changed manually; so, the
HR Master data was updated.
Witch kind of customizing or correction could be made in XI, to send
the correct structure to ECC?
Best Regards
Claudio

Hi Claudio,
In your case, there are perhaps two causes:
1. perhaps when you have import the idoc, for a strange reason, a bad metadata was created by XI. You can clean this one in tcode <b>IDX2</b> (Idoc metadata cache).
2. but it's also probably an error in your Message Mapping. Have you correctly manage segment E1PITYP?
Regards
Mickael

Question on RSSEND message type - based idoc sent from R3 to BW

Hi
I am not sure whether this is the right forum for this question, but my question is related to data exchange between R3 and BW and hence thought would ask the question here.
When data is extracted by BW - from R3, based on RSREQUST idoc , RSINFO is being passed based from R3 showing records passed back from R3, but I don't see RSSEND message type based idocs being sent back from R3.
I would like to see the RSSEND message type based idocs being sent back so that I can open and browse the contents of these idocs to cross the data here with the target system - i.e BW.
I have double checked outbound parameters in partner profiles in R3 - for RSSEND, it contains the right Z* idoc type , however I cannot see any RSSEND idoc being generated in R3 even though data is sent from R3 to BW.
Any idea what I am missing here ?

I dont think I understand what you are looking for , but in case you want to look for the IDOC in ECC and BI, follow these
steps.
In RSMO tranx --> menu -
> environment ---> ALE management ---> 1 . Datawarehouse & 2. Source System.
Thanks,
Ravi.

Message Mapping of IDOC "MATMAS.MATMAS05"

Hi!
I would like to execute the following message mapping for IDoc
MATMAS05 <--> MATMAS05.
What are the recommended fields to map?
Is the a button to automatically map the fields with the same names?
Thank you very much!
regards
Thom

Hi,
you could use the button "Map Selected Fields and Substructures if Names Are Identical"
it's explained here:
http://help.sap.com/saphelp_nw04/helpdata/en/49/1ebc6111ea2f45a9946c702b685299/frameset.htm
Or if you do it without a mapping:
simple IDoc to IDoc scenario with SAP PI
Regards
Patrick

Message type and idoc type

hi all,
i'm working on integration between sap and non sap.can anyone please tell me the message types and idoc types available for Funds Management and Project system modules.it will be of a great help,full points will be alloted imm.

What data you want to send / receive.
The site contains all message types which sap provides.
You can select your release and check in FI .
You can also check in tcode WE81 for available doc types .
Some of them I found are
GLCORE     Master data G/L accounts (CORE IDOC)
GLFETC     Request G/L accounts
GLM000     Test reduction GLMAST
GLMAST     Master data G/L accounts (master IDOC)
GLROLL     FI-GLX message type rollup
Your requirement is not clear as to what you want to send / receive with IDOCS.
Cheers

How To use External Message To Send IDOC From XI To R/3

we need to split one source message to several IDOC To
R/3,But Standard Imported r/3 idoc contains only one idoc per message,so we export the standart idoc to a
xsd file and change it to a multi "IDOC" segment structure and import back to xi again,after that,we create a message interface use the imported
message type and use it to send IDOC to r/3 via idoc adapter,but at the "call atapter" step it gernarate a
error:"Unable to interpret IDoc interface MI_IDOC_IN".
what we should pay attention to when use external message
to send idoc to r/3?
(when use the imported idoc message to send single idoc per message,it is no probelm)
thx

The way this works is:
1. In your Message Mapping use the External WSDL defintion that you loaded after tweaking the "IDOC" Occurance.
2. Then in your INTERFACE MAPPING use the orginal IDOC Name that you imported from R/3.
3. Use the original IDOC Name in Integration Builder too.
This should work.
Thanks
Ashish

Message type and IDoc type for PGI-GR?

hi all,
I have to send the PGI through ALE which have to create GR . So please mention the Message type , output type of message control and IDoc type?
Thanks
Vamshi

Hi,
The Idoc Types for Post Goods Issue are
MBGMCR01 / MBGMCR02.
Pls check the Message type in tcode WE82.
For output type GOTO transaction NACE-->Application V2.
hope this helps.
Regards,
Sharath
Edited by: sharath on Jun 24, 2008 7:16 PM

PI message packets effecting idoc events

Similar Messages

Maybe you are looking for