This website is not affiliated with, sponsored by, or approved by SAP AG.

Message Type Creation - One Header Different Lines Items

All postings related to SAP XI

Moderators: Snowy, thx4allthefish

Message Type Creation - One Header Different Lines Items

Postby jam123 » Tue Jun 04, 2013 4:42 am

Dear All SAP Gurus,
May be I am asking a beginner question But I need your clarification because I am novel to this subject.

I need to pass Purchase Order(PO) and Sales Order(SO) in single message from an external system to SAP. Therefore I have declared the Message Type as below. Advice me whethre this is correct and this is OK for a SOAP to PROXY scenareo.

OutBound Message
<Header 1...to unbounded>
<PO header Details>
<SO header Details>
</Header>

<LineItem 0...to unbounded>
<PO line Details>
</LineItem>

<LineItem 0...to unbounded>
<SO line Details>
</LineItem>


The messagw will contain 01 Header item NODE for both PO and SO and 02 different Line Item NODES for SO and PO Line Items.
This will be a SOAP to Proxy scenareo.

Plz Advice
jam123
 
Posts: 54
Joined: Sat Apr 18, 2009 12:29 am

Re: Message Type Creation - One Header Different Lines Items

Postby Baz » Tue Jun 04, 2013 6:15 am

Baz

AsPiRiNg tUlY iDiOt Image

http://www.catb.org/~esr/faqs/smart-questions.html

Image

check out my Podcasts http://dj-baz.podomatic.com
Baz
 
Posts: 4736
Joined: Fri Nov 08, 2002 5:54 am
Location: He's out there! somewhere!!!!

Re: Message Type Creation - One Header Different Lines Items

Postby jam123 » Tue Jun 04, 2013 7:27 am

Hi Baz,
Im not using BPM.

Or Can We have the message format as below also.
<Msg Type>
<PO>
<PO Header 1....Unboound></POheader>
<PO line Item 0....Unbound><PO line Item>
</PO>

<SO>
<SO Header 1....Unboound></SOheader>
<SO line Item 0....Unbound><SO line Item>
</SO>
</Msg Type>
jam123
 
Posts: 54
Joined: Sat Apr 18, 2009 12:29 am

Re: Message Type Creation - One Header Different Lines Items

Postby Baz » Tue Jun 04, 2013 8:43 am

then why not collect it in the proxy?

or you could use Soap > File > proxy

then you can use the append in the file adapter.
Baz

AsPiRiNg tUlY iDiOt Image

http://www.catb.org/~esr/faqs/smart-questions.html

Image

check out my Podcasts http://dj-baz.podomatic.com
Baz
 
Posts: 4736
Joined: Fri Nov 08, 2002 5:54 am
Location: He's out there! somewhere!!!!

Re: Message Type Creation - One Header Different Lines Items

Postby jam123 » Tue Jun 04, 2013 11:41 pm

Dear BAZ,
Thank you for the reply. Your reply helped me to think of a new scenareo BUT
This is a Synchronous Scenareo that user Needs the PO and SO number in reply as soon as he sends data from Legacy.
jam123
 
Posts: 54
Joined: Sat Apr 18, 2009 12:29 am

Re: Message Type Creation - One Header Different Lines Items

Postby Baz » Wed Jun 05, 2013 6:51 am

well for starters you do not have a synchronous scenario if there are two separate senders. that would never work. your initial requirements was the system has to wait and bundle the messages to send them, otherwise you would have two synchronous messages. one for SO and one for PO. if you think you can combine two messages into one and still process this synchronously you are mistaken.

you can quite easily call an asynchronous process after calling the proxy to return the messages to the legacy systems.

personally i think it is a mistake to bundle the two messages unless there is a specific requirement/request to do this.

if there is not, you can call the standard bapis to process these message synchronously and be done with it. if there is no specific reason or requirement there is no need to over engineer the solution. keep it simple and as standard as possible!
Baz

AsPiRiNg tUlY iDiOt Image

http://www.catb.org/~esr/faqs/smart-questions.html

Image

check out my Podcasts http://dj-baz.podomatic.com
Baz
 
Posts: 4736
Joined: Fri Nov 08, 2002 5:54 am
Location: He's out there! somewhere!!!!


Return to SAP Process Integration (SAP PI/XI)

Who is online

Users browsing this forum: No registered users and 1 guest





loading...


This website is not affiliated with, sponsored by, or approved by SAP AG.