Regarding Idocs and their corresponding message types

Hi,
Being am a trainee can u plz help in providing a list of Idocs and corresponding Message types that are using
in real time..
Thanks & Regards
Guna

Go to "jdk/include" on your drive and take a look at "jini.h". Note, mapping of C type to java types may be different for 16,32 or 64 bit machines. Using jinit, jboolean and others is recommended. On the other hand, if you are sure you won't use your C code in 64 bit or 16 bit environment just forget about it and assume int is java int, long is java long, signed char is java byte and so on. Pointers are more tricky - read carefully jini tutorials.

Similar Messages

My sender and the receiver message types structures are same.do I need to m

Hi all,
My sender and the receiver message types structures are same.do I need to mapping in this case.
If it is not required .Let me know in detail,How to proceed.
Thanks,
Srinivasa

Hi,
If is just to pass the message (as the sender source is the same as the receiver source),
first you should have the Message Interface of you message
then you should configure the Receiver determination, as the sender interface use your message interface and in the interface determination you can use the same message interface (same name). You dont have to add any mapping, just let empty and save. Just use one message interface for sender a receive.
Any questins let me know.
Regards,
Lpbuff

Query to Find all the Tables and their corresponding columns,dataType in DB

Hi all,
I need a query which can give me all the Tables existing in my DB and their corresponding Columns existed for those tables and Datatype for each column .
Thanks in Advance,
viajy

Hi,
For your user tables you can use USER_TAB_COLUMNS.
Just give DESC USER_TAB_COLUMNS at your SQL> prompt.
You will know on that object.
Regards,
Sailaja

How to generate reports of registered IP handsets and their corresponding extension on call manager 4.2.3

Hi
how to generate reports of registered IP handsets and their corresponding extension on call manager 4.2.3
I checked the route plan report and the generate report function on the BAT.. however it doesnt has the feature to generate only the registered IP phone with its coresponding extension
Thanks
Kind regards
Rachel

Call manager provides the called party with the extension or directory number of the calling party on a display. You can use the Calling Line ID Presentation field in the Gateway Configuration window to control whether the CLID displays for all outgoing calls on the gateway.Refer URL
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_administration_guide_chapter09186a008070e48b.html#wp1051056

Transfer (IDocs and TRFC): Missing messages or warnings

Hi,
While loading data from ECC to BI, I'm getting the following Error. It is for all DataSources...even for Full loads with 15 records also.
Requests (messages): Everything OK
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
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
Request IDoc : Application document posted
Data Package 1 : arrived in BW ; Processing : Selected number does not agree with transferred n
Processing (data packet): Everything OK
Data Package 1 ( 10 Records ) : Everything OK
Note: I tried with following options, so please don't repeate again.
1. No LUWS in ECC in SM58.
2. Connections are OK an dtested in SM59.
3. WE20 is also OK.
4. Job Finished successfully in ECC.
5. No Dumps in ST22 in ECC.
6. Dumps in BW in ST22.
Error Message is:
Probably the only way to eliminate the error is to correct the program.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"MESSAGE_TYPE_X" " "
"SAPLRSSM" or "LRSSMU36"
"RSSM_OLTPSOURCE_SELECTIONS"
7. Tried with BD87 in ECC and BI also.
Thanks
Ganga

Hi,
Every thing is fine. And I searched for OSS note and I found some notes but I'm unable to resolve it. My data Target is Cube and DSO's.
Note 852443 - Dump in include LRSSMU36 RSSM_OLTPSOURCE_SELECTIONS
Note 869628 - Constant WAITUPDA in SMQ1 and performance optimization
Note 901878 - Information IDoc Sent, but did not arrive
Note 913330 - tRFC LUWs are not created
Thanks
Ganga

Transfer (IDocs and TRFC ) Missing Messages

Hi,
I have taken INIT load and records were loaded successfully in the target system.Now when i run delta , the status goes Green but 0 records are loaded ,and also there is error as :
Requests (messages): Everything OK
Data request arranged
Confirmed with: OK
Extraction (messages): Everything OK
Data request received
Data selection scheduled
No data available, data selection ended
Transfer (IDocs and TRFC): Missing messages
Processing (data packet): No data
Subseq. processing (messages) : No errors
Process Chains : Everything OK
Other (messages): Everything OK
I have checked extractor in source system and it has records in it.
Edited by: Bhavna_m on Aug 26, 2011 12:57 PM

Hi,
Transact RFC error
tRFC Error - status running Yellow for long time (Transact RFC will be enabled in Status tab in RSMO).
Step 1: Goto Details, Status get the IDoc number,and go to BD87 in R/3,place the cursor in the RED IDoc entroes in tRFC
queue thats under outbound processing and click on display the IDOC which is on the menu bar.
Step 2: In the next screen click on Display tRFC calls (will take you to SM58 particular TRFC call)
place the cursor on the particular Transaction ID and go to EDIT in the menu bar --> press 'Execute LUW'
(Display tRFC calls (will take you to SM58 particular TRFC call) ---> select the TrasnID ---> EDIT ---> Execute LUW)
Rather than going to SM58 and executing LUW directly it is safer to go through BD87 giving the IDOC name as it will take you
to the particular TRFC request for that Idoc.
OR
Go into the JOB Overview of the Load there you should be able to find the Data Package ID.
(For this in RSMO Screen> Environment> there is a option for Job overview.)
This Data Package TID is Transaction ID in SM58.
OR
SM58 > Give * / user name or background (Aleremote) user name and execute.It will show you all the pending TRFC with
Transaction ID.
In the Status Text column you can see two status
Transation Recorded and Transaction Executing
Don't disturb, if the status is second one Transaction Executing. If the status is first one (Transation Recorded) manually
execute the "Execute LUWs"
OR
Directly go to SM58 > Give * / user name or background (Aleremote) user name and execute. It will show TRFCs to be executed
for that user. Find the particular TRFC (SM37 > Req name > TID from data packet with sysfail).select the TrasnID (SM58) --->
EDIT ---> Execute LUW
Thanks,
JituK

IDOC Types and their equivalent messages in EDIFACT and ANSI X12

Hi all, since I only have a list of messages in EDIFACT and ANSI X12 for release 4.6 B, I need to update the list from 6.0 version, but I don't have online support system to get it (OSS), it's note 104606 in OSS.
Can somebody give me a link to the full new updated list? Will surely give points with your helpful answers
Regards,

Hi,
Please check these perhaps they may help.
Mapping ANSI X12 to SAP Message Type and IDoc Type:
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), EDI - Inbound INVOIC posting configuration
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 logical message is DELINS (from the EDI standard ODETTE) or DELFOR, the IDoc type is 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 Ordering or order response (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 delivery in the SAP application, the logical message is DESADV, the IDoc types are DESADV01 (expires) or DELVRY01 and DELVRY02.
860 Ordering or order 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 logical message is DELINS (from the EDI standard ODETTE) or DELJIT, the IDoc type is 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.
Regards,
Ferry Lianto

BD87 idoc inbound error for message type HRMD_A

Hello there,
I am getting below error while fetching Inbound idoc in tcode BD87, see log below from ST22
Short text
    An SQL error occurred when executing Native SQL.
What happened?
    The error "-10328" occurred in the current database connection "LCA".
What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
How to correct the error
    Database error text........: "Mismatch of number of stream members for
     parameter (3) (application 6, database 9)."
    Database error code........: "-10328"
    Triggering SQL statement...: "EXECUTE PROCEDURE "SIM_SIMSESSION_CONTROL""
    Internal call code.........: "[DBDS/NEW DSQL]"
    Please check the entries in the system log (Transaction SM21).
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "DBIF_DSQL2_SQL_ERROR" "CX_SY_NATIVE_SQL_ERROR"
    "/SAPAPO/SAPLOM_CORE" or "/SAPAPO/LOM_COREU07"
    "SIMSCTRL_EXEC_COM"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
   Display the system log by calling transaction SM21.
   Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
   In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
The exception must either be prevented, caught within proedure
"SIMSCTRL_EXEC_COM" "(FORM)", or its possible occurrence must be declared in
the
Do we need SAP_APO in order to install LiveCache?
We have below landsacpe
- SAP ECC 6 EHP4 with SQL server 2005 S BACKEND
-LCAPPS Component release 2005_700 with SP
SAPKIBHD05.
- We dont have SAP_APO component
-SAP LiveCache system have MAXDB 7.7.04.29 as backend.
- Live cache client is installed on same SAP ECC system where we have SAP ECC EHP4 system.
any suggestion how to resolve it?
Mani

>
Mani wrote:
> I installed a standalone server and i need it only for SAP HR (specifically Idoc processing in SAP HR Human capital management module). But i am getting error while running ibound idoc process.
> So Do i still need SAP_APO component?
I never heard of this specific scenario for liveCache usage in the past 7 years working in SAP support on the liveCache component.
Might be useful if you provide some more details (documentation, notes, links) that describe this usage scenario.
In any case you will need to have a liveCache version that is compatible to your application ABAP coding.
The error message you posted indicates that your liveCache version does not fit your application version (or vice versa).
> I installed SAP MAxDB and LiveCache buid using Installation master DVD for SAP ERP. So i think i followed the right method as specified in installation guide.
Be precise, please. Which installation guide? There are hundreds of them - not THE installation guide.
> Secondly can you help me something specific to my problem in coding form?
Already did.
> i tried in LC10, using LCA monitoring i am not able to run SQLDBC trace under
> LCA >> LiveCache Monitoring >> Tools
> but i am not able to execute the same, is it a error or we need to configure something?
Well, the liveCache needs to be integrated into the LC10. You'd do this in transaction SM59 - but as you've followed an installation guide, this would have been covered in it...
> Operational status is active green light, below is file status.
>
>
KNLMSG     KnlMsg     1.098.697     28.01.2011     06:59:55     Database Messages     ASCII
> KNLMSGARC     KnlMsgArchive     8.192     28.01.2011     06:59:50     Database Errors     ASCII
> KNLMSGOLD     KnlMsg.old     342.663     28.01.2011     06:59:50     Database Messages (OLD)     ASCII
> KNLTRC     knltrace     6.209.536     28.01.2011     06:59:56     Database Trace (Raw/Binary)     BINARY
> BACKHIST     dbm.knl     570     10.01.2011     06:18:41     Backup History     ASCII
> DBMPRT     dbm.prt     133.843     29.01.2011     11:41:27     Database Manager Log File     ASCII
> DBMPAHI     L00.pah     214.225     10.01.2011     06:18:16     Database Parameter History     ASCII
> LCINIT     lcinit.log     15.299     28.01.2011     07:00:00     LiveCache Initialisation     ASCII
> LCINITCMD     lcinit.bat     3.047     28.10.2008     14:45:51     LiveCache Initialisation Script     ASCII
> LCINITHIS     lcinit.his     46.742     28.01.2011     07:00:00     LiveCache Initialisation History     ASCII
> INSTPRT     dbm.ins     863.981     10.01.2011     06:18:47     Installation Log File     ASCII
> DIAGDIR     File     0     10.01.2011     06:18:18     Diagnose History     DIRECTORY
> ANALYZER     analyzer     0     29.01.2011     00:00:36     DB Analyzer File     DIRECTORY
> LCTRC#init.his     lcinit.his     46.742     28.01.2011     07:00:00     LiveCache Trace (ASCII)     ASCII
> LCTRC#init.log     lcinit.log     15.299     28.01.2011     07:00:00     LiveCache Trace (ASCII)     ASCII
> LCTRC#_apo_version.txt     lc_apo_version.txt     164     28.01.2011     07:00:00     LiveCache Trace (ASCII)     ASCII
>
> any clue whats wrong?
> Mani
The only thing this tells us is: the liveCache instance itself apparently comes up and writes out the standard log files.
That's it.
As I already tried to explain, the problem seems to be the dependence between your application and the liveCache version.
Usually I'd recommend to open a support message for this, but the colleagues would (hopefully) ask the same questions as I did.
regards,
Lars

IDoc processing for same message type but diff extensions

Hi
I want to send idoc when a material is changed. Everything is in place and have also done a test scenario. In partner profile i had the message type linked to basic type and tested which is fine. Now i wanted to have one more idoc created for another extension having the same basic type and linked to the same message type. Have maintained the same in WE20 but when i executed BD10 i could only see one idoc been generated but i need to see two idoc (one for basic type and another for the extended) not sure where i'm missing. any pointers on it pls?

Hi ,
if you want to trigger the idoc two times for basic type& Extension..
1 ) you need to maintain WE20 Partner Profiles (This is good already you did)
--> But the Output type for Bsic type & extension type is same so output type is triggered Once so idoc is created One.
2) try to create another Output type in T-code NACE for extension then two Idocs is created one for Basic and another for Extension.
Regards,
Prabhudas

Idoc ORDERS05 with Custom Message Type

We want to use a Z message type for idoc type ORDERS05 to be able to separate a particular group of partners from other partners using ORDERS/ORDERS05.
The goal with our Z message type is to use the standard function IDOC_OUTPUT_ORDERS. The only problem I see is that this function checks the message type in form READ_SERVICE_PACKAGE. It would ignore this code since my message type is a Z and it's checking for message type ORDERS.
I was thinking of using a Z wrap-around function to perform the same code in form READ_SERVICE_PACKAGE if the message type is my Z message type.
I want to avoid creating a Z copy of IDOC_OUTPUT_ORDERS and all if the includes!!!
Any suggestions?

Hello Bruce,
The function module is associated with the process code.
Why do you need a new message type?
Regards,
Samir.

Outbound IDOC for sales order: message type, function module ?

Hi all,
is there a possibility to send out sales order data with an outbound IDOC (like sending an purchase order out with ORDERS.ORDERS05)
I've looked in WE20, for application V1 there are process codes like SD01, SD04, ... but the function modules behind are no existing on our system (release 500)
can anybody give me an little hint?
Thank you very much
best regards Hans

Hi George,
for every process code there is a function module attached you can see in WE41(t-code)..
double click on the Process code you will able to see the Function Module attached to Process code..
and also you can check it out in WE57 (t-code) link between the Function module and Message type and Idoc type..
Process code      SD01
Description       ORDRSP: Order acknowledgment, ORD_ID01 (SD_ORDRSP)
Function module   SD_EDI_ORDRSP_ORD_ID01
Process code      SD04
Description       DESADV: Shipping notif. with DES_ID01 (SD_DESADV)
Function module   SD_EDI_DESADV_DES_ID01
regards,
Prabhudas

How to get the IDOC name attached with message type (IDoc at receiver end)

Hello Friends,
I have configured the Order Confirmation Idoc.And the port used is XML_HTTP. in this port generally the idocs are sent to a java servlet.
So there the idocs are being created with name :- Idoc_no.XML
but i need to get the IDoc name prefixed or attached with the message type name, that the particular idoc uses.
waiting for your replies .
thanks,
jeevan

Hi Jeevan,
I am sorry for the confusion, the solution i provided is used when we go for XML FILe port. But when we go for XML HTTP port, this option is not available in SAP. So we need to check with the target system, whether there is any option available to read the file contents before saving , so that we can save the idoc with the required file name .
With my knowledge i assume why this option is not there for XML HTTP port is when we use XML HTTP port the idoc will be converted into XML and will be transported over HTTP protocol to an remote system which may be any type like XI, Java Servlet, Business connector, .Net etc. So in that case all the systems may not support the file name what we propose from the SAP. This is my assumption.
Please go through the help provided by SAP for XML Port types
http://help.sap.com/saphelp_nw04/helpdata/en/21/e9c975eb1911d6b2ea00508b6b8a93/frameset.htm
Please check with the Java guys who are working at the target end, whehter they may help you to resolve.
Thanks & Regards
Vijayanand Poreddy

Idoc serialization for custom message types

Hello,
We have a scenario where we need to serialize outbound messages where the message types are both custom and SAP standard. Can we serialize custom message types and how?

Hi,
you need to create a serialization group (in customizing) and assign all the IDocs (in specific order) to this group incl. your custom IDoc.
When data is transfered first a SERDAT01 IDoc will be sent, after this your IDocs have to follow in specific order. At last again a SERDAT01 follows and triggers the processing in the destination system.
Regards,
Kai

Regarding IDOC and ALE

Hii...experts...
I am new to the topologies IDOC,ALE and RFC connection...my requirment is when I create a sales order in one client (say) development..I want to create that sales order in another client (say) quality automatically, for this i want to create and trigger IDOC automatically..whether it is possible? if yes,can u plz give me the steps..
helpful answers will be rewarded..
Thanks Sugumar.G

Hi,
Salesorder IDOC
In this example a purchase is created, using the SAP standard functionallity for creating salesorders. When the salesorder is saved, and IDOC is automatically generated. Then we use the IDOC test tool to
create an order confirmation from the salesorder IDOC.
Create Vendor
Create customer
Create partner profiles
Create purchase order
Create the order confirmation IDOC
Create vendor
Create vendor using transaction code MK01. You can also use an existing vendor.
Vendor: T-BILHFN
Purch. org. : 001
Purchase organization may vary from system to system.
Create Customer
Create a customer using transaction VD01. You could also use an existing customer.
In the follwing example the vendor 3471 is used.
Create partner profiles
Create vendor partner profile
General data
Out bound parameters
Inbound parameters
Create customer partner profile
General data
Outbound parameters
Imbound parameters
Create purchase order
Use transaction ME21 to create the purchase order
To send an IDOC when the document is finished, go to Header -> Messages and
change the output medium to EDI.
Then select Further Data and change Dispatch Time to Send immediately. This will
create the IDOC as soon as the purchase order is saved.
Save the document.
Use transaction WE02 to check that the IDOC has been created without errors
Create the order confirmation IDOC
As the system has not been configured to handle the IDOC flow, the IDOC test tool
is used to simulate the flow. The Order IDOC is used as a template to create the
order confirmation IDOC.
Transaction code: WE19
Type the number of the Order IDOC in on the start screen and select menu IDOC ->
Create to create the template.
Change the control record
Note that the name of the port SAPTST may vary from system to system. The name can be seen in the Sender
port of the IDOC
Create new E1DK02 segment
The E1DK02 Document header reference data segment includes references to other documents.
The new E1DK02 segment should be created as a copy of the existing E1DK02, and at the same level.
Change the following fields of the record:
Qualifier: 002
Document item: 10
Qualifier = IDOC qualifier reference document = 002 = Vendor order
Document item =: Item number, see the item number on the purchasing document
Create E1EDP02 segment
The E1EDP02 Document Item Reference data includes references to other documents.
Create E1EDP02 as subelement of E1EDP01 Document item General Data
Qualifier: 001
Document: 4500010757
Document item: 10
Qualifier : IDOC qualifier reference document 001 = Customer purchase order
Document : Document number The number of the purchase order
Document item : Item number, see the item number on the purchasing document
Changing the ACTION field at header or item level
If you are working without a confirmation control key, the IDoc must have a processable action code at either
header or item level:
At header level, the segment field ACTION of segment E1EDK01 must be filled with the value '000' if the complete
purchase order is to be confirmed.
At item level, the segment field ACTION of segment E1EDP01 must be filled with the value '000' or '004' if the PO
item is to be confirmed.
Test IDOC
After the changes have been made, press the Standard Inbound button to generate the IDOC.
If no errors occurs go to transaction WE02 to check if the IDOC has been processed without errors.
If the IDOC has been processed without errors, then display the Purchase order (Transaction ME23). display the
item data and double-click on the item line. If all went well, you will now se that the field Acknowl. no. has been
filled out.
Pls. reward if useful....

IDOC - IDOC scenario with different message types

Dear Experts
I will like to have your expert opinion in the following question:
I have an IDOC -> IDOC scenario. Wherein at the destination system I have a message type which does not exist at the source system.
Also the IDOC type at destination system does not exist at the source system.
Let say, I will be creating custom message type at source system (Z****) and will also be creating the custom IDOC type (z****) with the same structure, definition as the destination.
Now my question is, even if there will be different message types and different IDOC types but with the same structure (the segment level definition
and field attribute remains the same at both the system). The difference lies with the names. And I have proper mapping though process code.
Will I be able to receive the IDOC correctly at destination?
Thanks & Best Regards

Hi All
I figured out the answer myself now.
You got to have same name for message type. All of you said this and this is rite.
Coming to IDOC type, I did not really got clear idea on this from this discussion.
But after working on a scenario, I learnt that, you can have different names for IDOCs, but provided that, whichever IDOC type the source system is sending, the same type must exist in your destination as well. Otherwise, system wont process your IDOC. But from mapping point of view, its upto individual how do thay handle mapping inside inbound process code for different idoc types / strucutes.
Lesson learnt by me, ideally try to keep same name for both logical message and idoc type at both source and destination. If possible try to keep the structure level also the same. This is my view, learnt it the hard way.
Cheers
Shane

Regarding Idocs and their corresponding message types

Similar Messages

Maybe you are looking for