on 10-17-2007 8:49 AM
Hi,
its urgent..
In our scenario
Message type is as follows
MT_filedata
.....sub_structure 1:1
........Data 1:1(the incoming data is variable field data in row format i.e.
HEADER TableName;COUNTRY_CD;BANK_CD;BANK_TYPE;BANK_NM;BANK_ID_CODE;
EXAMPLE 
BANK_EC_TBL;MEX;BANAMEX;1;Banco Nacional de Mexico;;
HEADER  TableName;COUNTRY_CD;BANK_CD;BRANCH_EC_CD;DESCR;BS_ACCOUNT_NBR;BANK_ID_CODE;
EXAMPLE
BANK_BRANCH_TBL;GBR;123456;TEST BLD SOC ID 8;Test Branch name 8;77777777;77777777;)
Now we have to read table name, on basis of table names we have to route to different target.
Here we are not using any Mapping Objects, as the Source & Target structures are same.
Nandan,
For this use <b>X-Path</b> in your RECEIVER DETERMINATION.
Just go through these blogs to know "how to implement X-Path".
/people/shabarish.vijayakumar/blog/2006/06/07/customise-your-xpath-expressions-in-receiver-determination
/people/shabarish.vijayakumar/blog/2005/08/03/xpath-to-show-the-path-multiple-receivers
/people/prasadbabu.nemalikanti3/blog/2006/09/20/receiver-determination-based-on-the-payload-of-input-dataextended-xpathcontext-object
/people/prakash.darji/blog/2006/09/22/using-xpath-statements-within-sap-netweaver-2004s-bex-web-application-designer--part-1
Regards,
Sarvesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
nandan,
you can give the condition at receiver determination step, so that if condition satisfies it will be routed to corresponding receiver.
If you are maintaining different interfaces then you could give condition at the interface determination.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.