Same message type in Diffrent Interface IDoc-HRMD_A

Hi All.
i am using standard message type HRMD_A iin one IDoc and have done coding in one of the Function Exit ..EXIT_SAPLRHA0_001
now if some other interface is also running using same satndard message type then how can i restritct my EXIT code to run for the 1st one only..like 1st one is running for country say Alaska and 2nd one for Ohio then how to make a check to diffrentiate between these two...as there is no Control data is populated before triggering this Function exit.i have done filteration in the exit like it will pass the data for the Alaska country only rest will be filtered out.but for the Ohio i want some other filyteration.Please assist.
Mona singh.

Hi Mona,
One question, just to see if I understood, the filter you want to use is by Company Code? or which is the field you want to use as a filter? You want some information to be sent to the destination and the other don't ?
Or you just want that the internal code in that Exit is to be executed for especific filter?
I ask, because there is a way to filter by company code the whole IDOC.
Regards
Edith

Similar Messages

Same message type and two different IDOCS need to be triggered

Hi,
I have two idocs with same message type,the partner profile is same.
Please tell if there is any way to handle this situation without changing the message type.
Please do the needful.
Thanks,
Nivedita

Hi
We can have same message type for different idoc types.
ex:MATMAS.MATMAS01
MATMAS.MATMAS02
MATMAS.MATMAS03
In the above example MATMAS is the same message type for different idoc types.
Thanks

Using same Idoc type & Message type for 2 Interfaces

Hi all,
we have 2 interfaces which uses same Idoc type, message type & Partner No.Only Process code is going to different according to the posting logic.
How can we differentiate both while posting idocs to not mess up each other .
Regards

Hi all,
Say example:
Interface 1 is invoice coming from legacy system to SAP and i have to use AAA.BBB Idoc
Interfaces 2 is accrual coming from legacy system to SAP and i have to use AAA.BBB Idoc
So i am creating partner No with LS_LEGACY and with 2 inbound entries one for each.
Even though i am using the same Idoc types but inside those the process codes are different because they are different in posting logic.
Issue:
From XI perspective i can't differentiate them saying like Invoice interface should execute the entry in the partner profile with invoice process code and accrual interface with accrual process code.
My Idea is to design like this...
Using the Message Code option, While creating partner profile give the MESCODE and in Mapping provide the same MESCODE.
So that even thought i am using the same partner No with same message type & basis types for 2 scenarios, the right interface will trigger the right process code based on the MESCODE mentioned in mapping by carrying the control record values
Please let me know ur views
Regards

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 - same message type

hello,
I have two idoc types named MATMAS04, MATMAS05.
(to MATMAS05 i have created an extension)
they are both in the same message type MATMAS.
i need to send the two idocs to the same system.
but, in transaction WE20 when i link the message type to the system i can create only one record of the message type. in all the administration tables for IDOCs i can see that i can send to idoc types under the same essage type but WE20 prevents it.
I don't want to create a new message type.
is there a way that i can use the same message type for different idoc types?
Regards,
Roi Grosfeld

Hi Roy,
This link might help u in idoc programming
http://help.sap.com/saphelp_erp2005/helpdata/en/78/21758d51ce11d189570000e829fbbd/frameset.htm
Hope this helps,
Regards,
Nagarajan.

Using the same Message Type

Is it possible to use the same Message Type in several Message Interfaces?
I have BPM which is using AbstractInterface.
I created this interface based on my Message Type.
I have got mapping exeption. Maybe it is because of using the same message type.

> Is it possible to use the same Message Type in
> several Message Interfaces?
sure!
> I have got mapping exeption. Maybe it is because of
> using the same message type.
I don't think so.
Stefan

Same message type

Hi,
is it possible to use the same message types in two different BPEL processes ?
If yes, could you show me an example ?
thank you & bye

Yes of course, just make sure the xsd's match. You can make sure the xsd's are the same in those BPEL processes by:
a) copy the .xsd's yourselves in each BPEL process (this violates the Edsger W. Dijkstra's design principle 'Avoid duplication of volatile information')
b) use a seperate BPEL process for storing all the common xsd's (unfortuately this requires that this process is deployed to the server before you can compile the other BPEL projects).
c) use svn:externals or a custom copy script that will make sure that there is only one source for the XSD's
The IT-eye article on Generate facade classes for multiple Oracle BPEL usertask payload structures at once might be usefull.
Regards,
PieterB

Multiple files (with same message type) into a single file

Dear All,
I am having multiple files(same message type) with details like header data and its line item details in each file. The structure of all the files will be:
File1    File2   File3
H1        H2      H3
L1         L1      L1
L2
L3
Now my requirement is that after every 10 hours all the files should be picked and merged (append) into a single file as target file. The structure of output file will be now like
H1
L1
L2
L3
H2
L1
H3
L1
Kindly guide on how to proceed on this with BPM or without BPM
Regards,
NJ

Now my requirement is that after every 10 hours all the files should be picked and merged
(append) into a single file as target file.
Check the use of "Availability Time Planning" of the adapter in your case
/people/shabarish.vijayakumar/blog/2006/11/26/adapter-scheduling--hail-sp-19-
If your requirement is to append you can do so by using the File Construction mode as Append in receiver File adapter
If your req is to do a N:1 mapping (i.e. merger) then develop a mapping program accordingly...
Regards,
Abhishek.
Edited by: abhishek salvi on Jun 3, 2009 10:30 AM

Multiple customers for same message type "invoic" and idoc type "invoic02"

Dear Experts,
I have SAP ALE process configured for single customer u2018Au2019 where I send invoic02 idoc (message type invoic) to the customer via PI server. Now I need to add one more customer u2018Bu2019 which require recepient determination. I am not sure whether this resolution of customer address at PI level or config is required at R3 itself.
I tried to maintain partner profile type as KU but it generates the error "No partner profile is maintained". For existing customer u2018Au2019 I am keeping the partner profile type LS.
I want to know the following:
a.Whether the recipient determination at R3 (config of partner profile we20)- if so what are the essential steps. Do I really need to shift partner profile type as KU?
b.Whether config is required at PI level itself- if so is there any pre-requisite config in R3 to support that in PI.
I hope my question is clear since this is my maiden attempt to seek solution from expert group.
Regards & Thanks

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

Multiple IDOCS of same message type To Single File

Hi Sap All.
here i have got a tricky situation of sending Multiple IDOC's of same type to a Single File via PI.
the Integration architect has created an Integration Gudeline of how to do this.
from the SAP-ECC side the follwing below are the steps thatr he mentioned
To allow IDOCu2019s to be processed sequentially in a queue, the queue processing option on the partner profile must be selected. In addition the rule name which is used to create queue names must be specified.
NB On the partner profile (for the partner / message type) you must also set the output mode as collect IDOCu2019s (it cannot be set to transfer immediately) u2013 This means the IDOCu2019s are created but not sent to out (to SAP PI)
As standard there are two rule names delivered CONSTANT:EDIQUEUE and FIRST_16_OF_MESTYP. These rule names are linked to a SAP function module and therefore custom queue names can be build either as an u201Chardcodedu201D name or based on the data in the IDOC.
The program RSEOUT00 should be run to transfer the IDOCu2019s to PI. The IDOCu2019s will be placed in the SAP ERP qRFC (rather than the standard RFC)
My Questions :
1. how and where we can select the Queue Processing option on partner profile in SAP-ECC as mentioned above
2.how and where we can define the Rule name as mentioned above
3.how and where we can set the output mode as Collect IDOC's in SAP-ECC as mentioned above
4.what does the EDIQUEUE and FIRST_16_OF_MESTYP will do and how they linked to SAP Function modules
will be waiitng for a the best solutions.
Regards.
Varma

/people/michal.krawczyk2/blog/2009/05/21/xipi-collecting-idocs--possible-ways-with-pros-and-cons--5-ways - you will need to do a collect

Same message type calling 2 maps

Hi Experts,
I want to send same Idoc messagetype for two different partners and want to call different map. And these idocs are coming from same SAP system.
Let say message type Orders , first partner PARTNER01 and second partner PARTNER02.
For PARTNER01 partner message mapping name is MM1
For PARTNER02 partner message mapping name is MM2.
When SAP is sending the message for partner PARTNER01 it should call MM1 and it should not call MM2.
Output files are also going to two different system.
Could you please let me what are the configurations are required in ID?
Thanks in advance for your valuable suggestion.
Regards,
Shubhankar

Hi Shubhankar !
You should enter your receivers (partner01 and partner02) in the receivers table of the receiver determination object. Here you can use the condition editor to detect which system should be the receiver based on content (payload, headers, etc.). Then to specify different mappings, you should create one interface determination object for each receiver system, in each interface determination object you should specify the interface mapping to be used. Please create one interface mapping object in repository for each mapping program (mm1 and mm2).
Regards,
Matias.

Defining input message Type for webservice interface with out input

Hi all,
I am configuring a scenario RFC -> XI -> Webservice. My sync webservice doesnot need any input. it genrates a random number which needs to be sent back to the RFC. How can i define an input message data type with out any data? As the interface requires both input and output data types in XI?
I tried a dummy data type with a single string input and didn't map it. but its not working because of name space issues. i specified a seperate XML name space in Message Type but i get a Target URL as the name space in the request which i provided in the SOAP reciever adapter.
Any help will be appriciated
Thanks and best regards,
Kulwant Singh

Hi
Can u chk the webservice request using test tools like stylus studio or xml spy and ensure that the same request is going out of XI .
make sure that you have changed the default xml namesapce in the target MT.
rgds
Arun

Same message type in different partner profiles in ALE

Hi,
I have a situation where we need to send an IDoc of message type ORDERS to two partners of type 'LS'. Configured partner profiles in WE20 and added message type for both the partners. Also configured the condition records.Now the question is how the system will know for particular vendors a particular partner 'LS' should be chosen? In condition records we don't have option to configure a vendor for a particular logical system.
Please advice.
Regards,
Krishna

For Vendors, why are you using LS, u need to use LI.

Problem in Message Type of Partner Profiles - IDOCS

Hi everyone,
I have created two Partner Profile's in WE20 attaching the corresponding Message Type with them. I have transferred one Message Type from one Partner Profile to another. When I save the model in BD64 and Generate the Partner Profiles from there I see that ''SYNCH" message type also gets added in the target Profile.
Can you please suggest why it happens and how to rectify this problem so that "SYNCH" message type does not get added anymore.
With warm regards,
Sandeep Panja.

Hi,
U can see SYNCH message type in all the partner profile.
The monitoring object is located in the same client A function module is called locally In this case no further Customizing settings are required
· The monitoring object is located in the same physical system but in a different logical system (client):
In this case you have to assign an RFC destination with a dialog user to the message type SYNCH in the current client for the client to be monitored.
http://help.sap.com/saphelp_nw70/helpdata/en/90/c4b523c4c411d2a5ee0060087832f8/frameset.htm

Acting as router and partner with the same message type

Hi All
Let A and B be two companies communicating with each other
via a company called R. Some MSCONS messages will just be
routed, some MSCONS messages will be kept by R, processed
and then routed on. The only way to know if it should be
processed or not is to read some of its fields and compare
them with current state in the database owned by company
R. If company A sends a MSCONS to B via R, the sending and
receiving identification id in the message will belong to
A and B, not R.
To make it more complicated, there are about 200 companies
communicating via R in the same way as A and B. Further
more, MSCONS is only one out of about 15 types of message
routed under these conditions.
Any suggestions on how to apply B2B to this use case is
most appreciated.
Best regards
Pär

Hi
I have a hard time to get following use case to work.
If company A sends an MSCONS to company B and C via R, is there a
way to configure B2B in R so that only one agreement is needed even though
company B and C have different interchange id's?After sending a MSCONS from A to R (host) and I look in reports, I find
that the sender, receiver, exchange protocol, document protocol, and business
action has been identified, but state is set to error. When looking into the log
I find following.
2007.09.25 at 17:32:47:516: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup Enter
2007.09.25 at 17:32:47:516: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = InterchangeReceiverQual, val = [ZZ]
2007.09.25 at 17:32:47:516: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [ZZ]
2007.09.25 at 17:32:47:516: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = InterchangeSenderID, val = [27700]
2007.09.25 at 17:32:47:516: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [Emix]
2007.09.25 at 17:32:47:516: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup Value and doc parameter don't match
2007.09.25 at 17:32:47:516: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = InterchangeReceiverID, val = [10001]
2007.09.25 at 17:32:47:516: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [null]
2007.09.25 at 17:32:47:516: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup Value doesn't match, doc parameter is null
2007.09.25 at 17:32:47:516: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = Standard, val = [EDIFACT]
2007.09.25 at 17:32:47:516: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [EDIFACT]
2007.09.25 at 17:32:47:516: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = InterchangeControlVersion, val = [2]
2007.09.25 at 17:32:47:516: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [2]
2007.09.25 at 17:32:47:516: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = ec_DataNodeName, val = [Interchange]
2007.09.25 at 17:32:47:516: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = InterchangeSenderQual, val = [ZZ]
2007.09.25 at 17:32:47:516: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [ZZ]
2007.09.25 at 17:32:47:516: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup return = false
2007.09.25 at 17:32:47:516: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup return = false
2007.09.25 at 17:32:47:516: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = TPName
2007.09.25 at 17:32:47:516: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = Actor
2007.09.25 at 17:32:47:516: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit Enter
2007.09.25 at 17:32:47:516: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit getLookUpError Key = key = [InterchangeSenderID] value = [27700] param = [Emix] Value = null
2007.09.25 at 17:32:47:516: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit getLookUpError Key = key = [InterchangeReceiverID] value = [10001] param = [null] Value = null
2007.09.25 at 17:32:47:516: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit NodeGUID = {7DDD0E19-7D9E-40AC-8DAC-A10BDB9AFB9E} position = 0
2007.09.25 at 17:32:47:516: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit Leave
2007.09.25 at 17:32:47:526: Thread-20: B2B - (DEBUG) iAudit report :
I do not want to add interchange sender id's 10001 and 27700 to
Document Protocol Parameters because then I make the document
protocol partner sensitive.
Any help is most welcome.
Best regards
Pär

Same message type in Diffrent Interface IDoc-HRMD_A

Similar Messages

Maybe you are looking for