Prob with Integration Process

[Former Member]

Hi,

Juz a simple file to file scenario with integration process. Ain't getting the output file for any Integration Process>??????

1) File is picked up. No problem with dat.

2) In sxmb_moni shows just 1 chequered flag for central client.

3) Receiver grouping schedule for outbound processing.

4) Inbound message still in green.

5) Check the return code in SXI_CACHE its is 0. No problem with that too.

Why is that integration process doesn't run for any scneario???????????????

<b>Cheers,

*RAJ*</b>

[Former Member · Accepted solution]

Hi Rajesh

Just checkout with Runtime Workbench. Have a look at the adaptors you have configured. It will show the error you are getting at output adaptor. Probably check with the path for output file.

Regards,

Gaurav Bhargava

[Former Member · Accepted solution]

Hi,

There is no problem with path.

In sxmb_moni it has to show 2 nodes. file sender and inpro.

Here it is showing only 1 i.e FILE. Outbound status is in redflag. XBQO$PE_WS90000007

<b>Cheers,

*RAJ*</b>

[Former Member]

1. check whether your IP is present in SXI_CACHE in green state .. and there is no activation error.

2. go the queue which has error ... select the message with system error message.. click the last column of the message entry... you should the exact error...

3. release the message from the queue..

4. or check the workfllow technical details...

[Former Member]

Hi,

An old aysnch -> synch process is running fine. Still didn't figure out what happ with this scenario.

<b>Cheers,

*RAJ*</b>

[Former Member]

Hey

could you please check in sxmb_moni_bpe and see the log.

thanx

Aamir

[Former Member]

Hi,

Sorry 4got to mention about that.

Wrokflow started -> status -> error.

Send step -> system error.

Checked the send send in integration process. Nothing wrong with parameters or mapping.

<b>Cheers,

*RAJ[/b<b>]*</b>

[Former Member]

what error it is giving in Send step??? Have you checked in queue? Have u taken cache refresh??

In work flow, is there any error in send step??

[Former Member]

Hi,

Send step -> An empty container element was specified when sending.

There are no issues as far the scenario is concerned. Using a absend refering to file msg type.

Outbound Queue -> No messages everything is fine.

Inbound Queue -> Status -> system fail

Tried to deregister and register queue . Fine . While activating got a error

Inbound queue.

Error while activating queue XBTI*

Any clues?

<b>Cheers,

*RAJ*</b>

[Former Member]

Hi Rajesh,

>>>An empty container element was specified when sending.

Seems like your mapping didnt execute.

let us know the steps in BPM?

Regards,

Sumit

[Former Member]

Hey Sumit.

Tested the messge mapping no probs there.

Very simple int pro had done scenarios like this n number of ways in old server no problems there.

SRC -> REC -> SEND -> TAR

REC -> recabs

SEND -> sendabs

Data is reaching send step i can see that in graphic description of INT PRO. There it throws are system error.An empty container element was specified when sending. Thats not possible in the first case as the data is send by the rec step to send step.

In SXMB_MONI though initially it has a chequered flag but at OUTBOUND -> PE ->OUTBOUND STATUS ->RED. Queue XBQO$PE.

QUEUE -> register -> deregister -> activation.Done.

Where is the damn prob.

Cheers,

*RAJ*

[Former Member]

Logically delete your IP and then send message again..

[Former Member]

Hi,

Delete >? where -> IR / ID ?

<b>Cheers,

*RAJ*</b>

[Former Member]

Hi Raj,

Your recabs & sendabs interfaces uses the same message type ??

If not you need to have a mapping step in between.

Go to transaction code SWWL .

Remove the filters TYpe, Status, Agent and exectute. Delete the process with errors and run the scenario again.

Regards,

Sumit

Message was edited by:

Sumit Khetawat

[Former Member]

Hi,

Nope both ABSREC and ABSSEND use the same message type as of the source.

Interface mapping between abssend -> target interface.

<b>Cheers,

*RAJ*</b>

[Former Member]

Hi,

Did u delete the old work items ??

If not do the same and run the scenario.

Also run this t-code SWF_XI_SWI2_DIAG and find out your process and check out the error in detail.

Regards,

Sumit

[Former Member]

Sorry for the late reply.

Logically delete means... Go to your message in SXMB_MONI. Click on PE. Go to Technical Details. Go to work item. In that got to Edit- Change. There u will find logically delete option. When u will delete your process might be your scenario will work.

Also check your mapping output. Just check that message is getting populated in outbound container or not?You can check this in technical details tab. If not that means your mapping is not executing properly. Also paste your inbound payload on this thread. Also check the payload which is going to PE is not blank. I think the data which is going to PE is blank.

In case of any problem plz get back to me. Bcoz Inmy scenario I was also facing similar type of problem but it got solved.

-Gouri

Award points if useful.:)

[Former Member]

Make sure that Interface mapping is created based on outbound asynchronous interface and abstract interface. That is target interface should be abstract.

[Former Member]

If your source and target data type are same then u will require only 3 interfcaes. Outbound, inbound and abstract. And IM will be between Outbound and Abastract. make sure target will be abstract.

If your source and target data types are different then u will need 4 interfaces. outbound, inbound, Out-Abastract, and IN-abstract.

Here MM will be between outbound and inbound while IM will be between Out-Abastract, and IN-abstract.Also u will have to use transformation step in this.

I think problem is with mapping.

-Gouri

Award points if useful

[Former Member]

Hey Gouri,

Thanks for the interest show i didn't knew abt logical delete yet so was good to learn. Thanks a lot for that.

Source and target are different in this case.

What i am doing is

Src interface:

1) data type

2) msg type

3) src MI outbound, Rec Abs, Send abs (both abs refering to src msg type )

4) int pro with 2 steps rec and send

5) Msg map between src and target msg type.

6) Inter Map between sendabs and target interface

As the mapping is between is send abs and target interface no need of transformation step.

Target system

1) data type

2) msg type

3) src MI Inbound.

This scenario did work before........lng tym bak

Mapping is fine no errors.

Cheers,

*RAJ*

[Former Member]

Hi,

After logical delete the PE show chequered flag kewl but didn't get the output file ?

Processed another message same error so had to execute logical delete for every message >? any way to avoid it

<b>Cheers,

*RAJ*</b>

[Former Member]

Hi,

You got the prob bingooo...

Checked technical details

Rec step -> can see the header details but payload is blank ?

In sxmb_moni can see the payload being sent.

Send step->

message NOT getting populated in outbound container . Definetly as rec step doesn't have paylaoad right ?

AHH NOW ANY QUICK FIX SOLUTION

Cheers,

*RAJ*

[Former Member]

Why u are creating two abs interfaces??? It is not at all required...

Container elements are two or one?

And what is there abs type interface?

[Former Member]

Not req yeap i know this is not a production scenario so just testing it with 2 step types.

2 container elements. and yes they are of abs type. Some very complex int pro scenarios are working fine.

[Former Member]

Just Try by declairing both containers of type send abs.

[Former Member]

Let me in to the PLAY..

HI rajesh,

I could suggest u onething, check in sxmb_moni whethr the source payload is filled while it goes to IP .

Check whether the abstract interface has the same structure as it receives.

go to technical details of IP and its log and check the container element by rclick and go through all the contexts.

[Former Member]

Hi Rajesh,

first delete the entries and then try to register queues using Tcode SMQR

thanks

sandeep