WC, ESI, SAP

[cadjett]

Quick Question.

Current client is trying to connect/integrate WC 10.1 to SAP.

The current issue is getting Serial Number with multiple ranges across to SAP.

If there are ranges such as: 1-20,30-40,70-100. Only the 1-20 is getting across.

Has anybody had this issue & resolved it & if so, how?

I have read where this works for Oracle ERP, but not for SAP.

I seen a suggestion that BAPI edits might resolve this,but the client is trying to avoid customizations on WC or SAP.

Can the resolution be resolved in Tibco (customized or reconfig)?

Any help would be appreciated.

Larry Jett
datajett@aol.com, cadjett@aol.com

[cadjett]

Anybody??? LOL

[atwood]

https://www.ptc.com/appserver/cs/view/solution.jsp?n=CS154635

FWIW, that article doesn't seem to indicate you could address multiple ranges without a customization or enhancement.

Tim Atwood

PTC Enterprise Deployment Center

[cadjett]

Thanks Tim,

I had seen https://www.ptc.com/appserver/cs/view/solution.jsp?n=CS154635 before.

I was hoping some one had found the route to cover multiple ranges, through either setting, flag, code, etc.

Thanks though.

L Jett

[cadjett]

Next ERP Pop Quiz:

Still in early stages, but when we send send wtpart, ecn, bom to sap, the data gets to & shows in SAP, but the ESI workflow shows Running in last task before sending success notification, so we never receive the email or other.

Anybody ran into this issue?

L Jett
cadjett@aol.com,datajett@aol.com

[ssenthil]

RTM workflow has a sync robot that waits for a success/failure event for the
message posted. Please check the release history of the published object. If
the release history is not updated that means the return message from SAP is
not properly received by the ESI. Following are the sequence.



1. Releasable object reaches a specific lifecycle state that triggers the
RTM workflow.

2. RTM workflow pre validates the releasable and generates response XML

3. Response XML is posted to Tibco message queue

4. Tibco processes the message and invokes SAP adapter

5. A success/failure message is written to Tibco a queue.

6. ESI is subscribed for the queue and parses the message

7. Release history is updated and a success/failure event is emitted.

8. RTM workflow sync robot listens for the event and sends notification/task
for fixing the issue.



From your description, something is failing in 5 - 8

HTH



Thank you and have a great time.

Best Regards

Swamy Senthil

Principal Solutions Architect, Swasen Inc

swamy.senthil@swasen.com(Email); 909 800 8423(M); 973 324 2729(W); 866
908 6561(F);

[arajagopal]

Jett,

In your original post, asked that customizing or configuring TIBCO is an option, does that means WC ESIResponse.xml has all range info or just having only first range value 1-20? Can you clarify?

IfESIResponse.xml not having full range values, I think solution has to be done on Windchill side first and then take a look how TIBCO respond to it.

Also uploading one of your esiresponse xml file and expected result xml file should help others to suggest some possible solution.

[Gandhavalla]

Hi

I implimented same to same solution for St. Jude Medical.. Please check with SJM for mode information..

warm regards

Sreeni

esisreeni@gainformatics.com