Ack for Inbound messages

Hello All,
I already worked with acknowledgements of outbound messages(and processing them in orchestration in case of failure etc). But now I have a requirement to generate acknowledgements for inbound messages, like I need to generate a custom outbound acknowledgement
for every inbound message. I know it can be done in an orchestration, but is this something can be done with pure messaging. For inbound message, the transport is FTP(it would have been good if it was a HTTP/SOAP port).
(I'm not doing any EDI here, so, I'm not talking about EDI 997, this is purely BizTalk messaging.)
Thanks
Bhava

You can still do it Messaging only, but it would require a custom Pipeline Component to create the ACK message on the Send side.
In this scenario, an Orchestration would just be easier. The one issue you might face is whether or not the FTP Adapter will write a 0 length file. Sorry, I just don't recall. The File Adapter will not, that's for sure.

Similar Messages

To map batch number to serial number for inbound message type WMMBXY

Hi Gurus,
Can anybody guid me how to map batch number to serial number for goods receipt inbound EDI 861 message type WMMBXY .
And can tell me how to assign serial number in Purchase Order for serialized product for perticuler Batch number.

hi dsk,
thanks for your earliar reply,
actually iam working on sapscript there i want to add batch number ,but i am not able to clear my doubt from where i get this.
how can i map batch number with corresponding to PO num ber, '
in the report i used structure vbplp with field charg"(batch num).
also i want to know from which table i can get customer part number and Po number .
how can i add batch num ,..
from which table or with which field i can compare itr to get .
sunny

Alert for Inbound message errors

Hi
We are updating the inventory using ProductActivityNotification inbound XML message from SAP PI. But when it fails due to some error(e.g Shipping party invalid) , we need to raise an alert or send mail, Could you please let us know how to configure it.
Regards
Anandan

Hi Anandan,
You can make use of the below link to configure your
scenario
http://help.sap.com/saphelp_scm70/helpdata/EN/5b/5d1741b393f26fe10000000a1550b0/frameset.htm
Regards
R. Senthil Mareeswaran.

Mapping for INBOUND sales data

Hi All, I am working on SAP-POS integration for a retailer. My question is on mapping of inbound sales data with the Idoc - wpuums01. Partner profiles are of type - Customer - and also there will be a seperate partner profile for each store.
But, Inbound POS data has store number and idoc doesn't have store number in segments E1WPU*. IDOC has sender partner number , which is store number in this case, in EDI_DC40 segment.
I think, we deactivate EDI_DC40 segment for inbound messages. If this is the case, how do we map store number in pos file with IDOC. If we keep EDI_DC40 segment active, do we have to map the fileds like tabnam, mestyp, idoctyp, sndpor, sndprt, sndprn, rcvpor, rcvprt, rcvprn etc...
thanks in advance for your inputs.

hi,
>>>>Can I select "apply control record values from payload" OR select "take receiver values from payload".
you can select take from payload and set sender
(two things) and the store number can be dynamic (from payload)
IDOC adapter config that you're looking for is described in my book:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

Rosettanet Inbound message erroring with error

Hi,
We are getting ""PI with the name 'xml' can occur only in the beginning of the document" error for inbound messages in Rosettanet format. This is happening for only one TP, but there is no difference in the message format except few extra lines.
The TP is confirming that the message is getting generated using "BizTalk" server.
Any suggestion to fix the issue is highly appreciated.
Thanks,
Adarsh

Adarsh,
XML file is invalid. Make sure that "<?xml version="1.0" encoding="UTF-8" ?>" is the first line in the XML and there are no characters/spaces before it. There should be only one occurance of <?xml in the incoming XML and that too in the prolog I mentioned above. An following occurrence must be escaped using CDATA tag.
Regards,
Anuj

IP_MESSAGE_PARAMETER for inbound

Hi,
Am using B2B for Inbound messages when i send the message from outside to B2B,am getting following error
weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@1025142] [userId: <anonymous>] [ecid: 0000ITYFXry7MAYVLqBT8A1Bb^1000002I,0] [APP: soa-infra] Error -: B2B-50083: Document protocol identification error.[[
at oracle.tip.b2b.engine.Engine.identifyDocument(Engine.java:4203)
at oracle.tip.b2b.engine.Engine.processIncomingMessageImpl(Engine.java:1850)
at oracle.tip.b2b.engine.Engine.processIncomingMessage(Engine.java:1395)
at oracle.tip.b2b.engine.Engine.incomingContinueProcess(Engine.java:3216)
at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:2960)
at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:2706)
at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:540)
at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:200)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:77)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
[SRC_CLASS: oracle.tip.b2b.system.DiagnosticService] [APP: soa-infra] [SRC_METHOD: log] class oracle.tip.b2b.metric.B2BMessageProperties[[
fromTP : null
toTP : null
DocumentProtocol : null
DocumentProtocolVersion : null
DocumentType : Acknowledgement
Agreement : null
MessageSize : 12095.0
MessageState : ERROR
FromEndpoint : http://192.168.200.30:8080/as2/HttpReceiver
FromEndpointProtocol : HTTP
FromEndpointStatus : CONNECTED
ToEndpoint : http://192.168.200.188:8001/b2b/httpReceiver
ToEndpointProtocol : HTTP
ToEndpointStatus : CONNECTED
Application : null
Application : null
Composite : null
CompositeVersion : null
Service/Reference : null
So my question is how can i set the above parameter for inbound files.
This is an urgent,please help on this.
Thanks,
Arun Jadhav

Hi Dheeraj,
I am using custom document type.
Am trying to send one document from the AS2 server to B2B, but on B2B am getting document protocol Error.
I have also created the channel for my trading partner which in address of AS2 server
In above mention error log you can see that B2B is not getting the required parameter values.
How does the B2B know that particular message is for any of the document type created in B2B.
Thanks,
Arun Jadhav.

[svn] 1751: Bug: BLZ-174 - MessageClient.testMessage() is incorrectly doing a string compare for the subtopic header of an inbound message against the subtopic value (which may contain wildcards) that the Consumer is using.

Revision: 1751
Author: [email protected]
Date: 2008-05-15 14:21:43 -0700 (Thu, 15 May 2008)
Log Message:
Bug: BLZ-174 - MessageClient.testMessage() is incorrectly doing a string compare for the subtopic header of an inbound message against the subtopic value (which may contain wildcards) that the Consumer is using.
QA: No - customer verified the fix.
Doc: No
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-174
Modified Paths:
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/MessageClient.java
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/services/MessageService.java

If you create a metadatatype with a single metdata block, and you reference that in your vm/cm cell attribute using a *one* based index, Excel seems to see the link and it honors it when saving the spreadsheet.
So, I ended up with something like:
<c ... cm="1"/> (I'm dealing with cell metadata, but the concept is equivalente to value metadata)
<metadataTypes count="1">
  <metadataType name="MyMetaType" .../>
</metadataTypes>
<futureMetadata count="1" name="MyMetaType">
  <bk>
    <extLst><ext
uri="http://example" xmlns:x="http://example"><x:val>87</x:val></ext></extLst>
  </bk>
</futureMetadata>
<cellMetadata count="1">
  <bk><rc
t="1" v="0"/></bk> 
</cellMetadata>
Hope this helps.

EDI Message Type for Credit Memo inbound message

Hi Experts ,
We have ECC6.04.
We configured Incoming vendor invoice idoc ( Message Type - INVOIC, Basic type - INVOIC02) which is working fine. We also have Credir Memo incoming message ( Message Type - GSVERF , Basic type - GSVERF03 , Processing code- GSVE , FM-IDOC_INPUT_GSVERF_START and assigned this FM to Object Type- BUS2094)
I am using same IdoC in WE19 that of Invoice, which successfully posted and editing the BSART as CRME and entering the Messgae type GSVERF , but when I am posting it system is giving error
No record exists in T661W for vendor 2000001 , plant , unloading pointMessage no. V4032
Diagnosis
The system could not determine a sold-to party as no record has been specified in Table T661W for the displayed supplier, plant, and unloading point values.
System Response
IDOCS processing is terminated.
Procedure
Please create a record in Table T661W for the above values and restart the IDOCS planning from electronic mail.
and
EDI: Syntax error in IDoc (segment cannot be identified)Message no. E0078
Diagnosis
The segment E1EDK04 does not occur at the current level of the basic type GSVERF03 (extension ).
This error can have several reasons:
The segment E1EDK04 is assigned to a group whose header segment does not occur.
The segment E1EDK04 does not exist in the syntax description of the basic type GSVERF03 (extension ).
The sequence of segments in the group in which the segment appears is incorrect.
Previous errors ('mandatory' segment or group missing) may be due to this error.
Procedure
Please check the IDoc or the syntax description of the basic type GSVERF03 (extension ).
Th table T661W is for Vendor, partner decribtion, Sold to party, Unlaoding Point. So I am not getting whsy sold to part relevant table ssytem is asking to make entry ?
Can anyone please suggest/help me what is the problem and solution on this ?
Thanks
NAP

Hi ,
Currently we are using Message Type - GSVERF , Basic type - GSVERF03 , Processing code- GSVE , FM-IDOC_INPUT_GSVERF_START and assigned this FM to Object Type- BUS2094)..which is giving above error. I just found that process code GSVE is for Outbound message
Can any one suggest / confirm what should be exact Message Type , Basis Type, Process code and Funct. Module requiered for processing EDI inbound message in MM - Logistics Inv Varification ?
Thanks
NAP

What is the logical message type for Inbound Credit Memo (MM)

Hi Folks,
What is the logical message type for Inbound Credit Memo (MM)
Plz explain.
Thanks,
Matt

Hi Mat,
The logical message types are as follows.
/DSD/HH_CREDITDATA             DSD Credit Exposure and Credit lLmit
CREADV                         Credit memo display
CRESTA                         Copy credit status (DebtorCreditAccount)
SBINV                          Credit memo procedure with invoice creation
SBWAP                          SD Credit Memo Procedure with Automatic Postin
You can search for message types in database table EDMSG.
Regards,
Vimal.

Inbound Idoc for own Message type

Dear All,
I have created a message type for outbound and sent data to the Java System.But when distributing in BD64 inbound parameters are not getting created.
For inbound idoc if i am creating a new message type,How i can get data from external server and commit it in database.
We have to write any program as we do for outbound?
Another issue outbound idoc is in waiting status i have to process it in BD87.How i can sent it immediately and in partner profile, distributing in module view BD64 i have given Transfer IDoc Immediately.
PLZ reply ASAP.
Thanks & Regards,
Arun.

Dear rhea,
I want to receive the IDOC data for message type WPUUMS from a java server. Currently i am working on sample values for segments
E1WPU01
E1WPU02
E1WPU03
E1WPU04
E1WPU05
E1WXX01
I am facing problems in passing the correct values .
Its throwing a error message status 51.(Application document not posted) IDoc not fully processed.
can you help me with some dummy data for all the fields in the above segments.
reply ASAP
regards
arun

SOAP version for B2B HTTP inbound message in SOA Suite 11.1.1.7

Is there a way to find out the SOAP version supported by B2B HTTP inbound message in SOA Suite 11.1.1.7? Has there been a upgrade of SOAP version to SOAP 1.2?
The reason behind this assumption is because we are facing following error when an external service posts an XML message enclosed in SOAP envelope (SOAP 1.1) to B2B Sync Receiver Servlet:
Mime Header Content-Type: text/xml requires SOAP envelope namespace
Since SOAP headers are already added in the message we are not expecing to face such issue. As per my understanding this issue maybe seen when there is a SOAP version mismatch.
Moreover, this issue is not seen when this external service posts the same SOAP message to B2B Sync Receiver of SOA suite 11.1.1.6.
Any help would be highly appreciated.
Thanks,

I resolved the issue by myself, The connection factory which I was referring was duplicated. Hence messages were not dequeueing.
I would be able to found the issues by creating a similar test case scenario.
Cheers,
B

No item could be determined for Inbound for TO message No.L3898

Hi folks!!
While doing TO for inbound, I am getting following error No items to be placed in storage could be determined.
While if I tried to create TO with reference to GR, system is allowing me to create TO.
Please let me know what are the settings required to create TO for Inbound delivery.
Best regards

Hi,
LT03 is used to create TO WRT outbound delivery and even the path for that is under Outbound delivery
Logistics -->Logistics Execution -->Outbound Process -->Goods Issue for Outbound Delivery -->Picking -->Create Transfer Order -->LT03 - Single Document
LT0F is used to create TO WRT inbound delivery.
Once the Inbound delivery is created, then check whether a material document is created. I.e in Status overview Total Goods movement status should be C. if this is A then in document flow you can see that the inbound delivey is open.
Execute Goods Receipt for the inbound delivery and then execute LT0f.
This should solve your problem

Error receiving AS2 message from partner: B2B-50037: B2B inbound message processing error

B2B/SOA 11.1.1.6.0
We are setting a new trading partner and when we started document transmissions we are getting errors on the inbound messages: B2B-50037: B2B inbound message processing error.
The attachment shows the relevant lines from the soa log and diagnostic log files. Here is the error detail that shows:
[URI: /b2b/httpreceiver] Error -: B2B-50037: B2B inbound message processing error[[
Error -: B2B-50037: B2B inbound message processing error
        at oracle.tip.b2b.engine.Engine.processIncomingMessageImpl(Engine.java:3143)
        at oracle.tip.b2b.engine.Engine.processIncomingMessage(Engine.java:1650)
        at oracle.tip.b2b.transport.InterfaceListener.onMessageLocal(InterfaceListener.java:403)
        at oracle.tip.b2b.transport.InterfaceListener.onMessage(InterfaceListener.java:214)
        at oracle.tip.b2b.transport.basic.TransportServlet.doPost(TransportServlet.java:754)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
        at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
        at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
        at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
        at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
        at java.security.AccessController.doPrivileged(Native Method)
        at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
        at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
        at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
        at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
        at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
        at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
        at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
        at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
        at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
        at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
        at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
        at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
        at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
From the b2b_wire_message we get these Protocol_Transport_BINDINGS:
ChannelName=TransportServlet
Reverse-Via=LIN-ISA1
AS2-To=accobra.....
Date=Fri, 26 Sep 2014 05:46:17 +0000
AS2-Version=1.2
AS2-From=K.......
Disposition-Notification-Options=signed-receipt-protocol=optional, pkcs7-signature; signed-receipt-micalg=optional, sha1
Disposition-Notification-To=http://<ip&port>/as2in
Message-ID=<[email protected]>
MSG_RECEIVED_TIME=Fri Sep 26 00:46:17 CDT 2014
ECID-Context=1.0050z5j^buc6yGn6wnZf6G0002f60007bt;kXjE1ZDLIPGIj2QCYV8QoKSSmLRO_PQT_IS
Content-Type=application/pkcs7-mime; smime-type=enveloped-data; name=smime.p7m
Proxy-Client-IP=172.17.25.101
MIME-Version=1.0
User-Agent=e-integration AS2 Server V 6.1.8
X-Forwarded-For=172.17.25.101
Content-Length=3602
Host=nalinsoa05.abd.ad.acco.com
x-weblogic-cluster-hash=QoZzGUzdcjBD5fGIE8Uos5abiHI
EDIINT-Features=multiple-attachments, CEM
Connection=Keep-Alive
X-WebLogic-KeepAliveSecs=30
X-WebLogic-Request-ClusterInfo=true
The message creates a wire message, business message, and an application message.
What doesn't happen is no MDN gets sent back to the partner. It should be a synchronous MDN.
We have double checked the certificates on both ends and they are OK.
The document and Agreement get recognized OK:
Refer To Message
Refer To Message
Sender Type
AS2 Identifier
Sender Value
K. . .
Receiver Type
AS2 Identifier
Receiver Value
accobr. . .
Sender
K. . . l
Receiver
ACCO . . .
Agreement Id
K. . .l_EDI_X12_4010_856_856Def_Inbound
Agreement
K. . .l_EDI_X12_4010_856_856Def_Inbound
Document Type
856
Document Protocol
EDI_X12
Document Version
4010
Message Type
REQ
Direction
INBOUND
State
MSG_ERROR
Acknowledgement Mode
SYNC
Response Mode
ASYNC
Send Time Stamp
09/26/2014 12:46:17 AM
Receive Time Stamp
09/26/2014 12:46:17 AM
The error is vague enough to provide little or no help in locating the root cause of the issue.
Any assistance in providing information on how to get this working would be greatly appreciated.
We do have dozens of other AS2 partners working in this instance just foe reference. We are just having issues with this new partner setup.
Thank you.
Regards,
Ken

Ken,
I am observing the Ack Mode is set as "SYNC" . This is selected by default. This option is available in the channel configuration section
If the usecase is not SYNC, please change as ASYNC and test. It should work.

Inbound Message Fails with Send Exp"

We are on 10.1.2.0.2 and tryting to test (ebms ) outbound/inbound messaging with a trading partner. The outbound from us to TP works great, but on inbound from the TP we are seing the following errors: (This works on 10.1.2.0.0)
Machine Info: (devb2b.helenachemical.com)
Description: B2B adapter general error
StackTrace:
Error -: AIP-50031: B2B adapter general error: Error -: AIP-50025: Repository error : Error -: AIP-50547: Trading partner agreement not found for the given input values: From party[NAME] "DEST Partnre", To party[NAME] "SOURCE Partner", Business action name "SendResponseEnd"; also verify agreement effectiveToDate
     at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1735)
     at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2294)
     at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2193)
     at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2148)
     at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:500)
     at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:348)
     at java.lang.Thread.run(Thread.java:534)
Caused by: Error -: AIP-50025: Repository error : Error -: AIP-50547: Trading partner agreement not found for the given input values: From party[NAME] "DEST Partner", To party[NAME] "SOURCE Partner", Business action name "SendResponseEnd"; also verify agreement effectiveToDate
     at oracle.tip.adapter.b2b.tpa.RepoDataAccessor.getAgreementNameByBaTPType(RepoDataAccessor.java:1852)
     at oracle.tip.adapter.b2b.tpa.TPAIdentifier.identifyTPA(TPAIdentifier.java:167)
     at oracle.tip.adapter.b2b.tpa.TPAProcessor.processTPA(TPAProcessor.java:495)
     at oracle.tip.adapter.b2b.tpa.TPAProcessor.processIncomingTPA(TPAProcessor.java:226)
     at oracle.tip.adapter.b2b.engine.Engine.handleExceptionBeforeIncomingTPA(Engine.java:3568)
     at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1614)
     ... 6 more
Caused by: Error -: AIP-50547: Trading partner agreement not found for the given input values: From party[NAME] "DEST Partner", To party[NAME] "SOURCE Partner", Business action name "SendResponseEnd"; also verify agreement effectiveToDate
     at oracle.tip.adapter.b2b.tpa.RepoDataAccessor.getAgreementNameByBaTPName(RepoDataAccessor.java:2176)
     at oracle.tip.adapter.b2b.tpa.RepoDataAccessor.getAgreementNameByBaTPType(RepoDataAccessor.java:1839)
     ... 11 more
Any ideas on what is different in the newer version of B2B
Thanks
PT

Hi Ramesh,
Found this issue- in the new release the Business Action name and choreography name must match to work with TP on custom document over ebms.
We still have issues,,, the TP's that are working currently on 10.1.2.0 are no more working. For example:
The following wire envelope was sent from one of our TP:
--MIME_boundary
Content-ID: <1dac9c73-bba3-4fc3-a756-0134872b03d2ebxml-Header>
Content-Type: text/xml
<?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:eb="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd" xmlns:xlink="http://www.w3.org/1999/xlink" xsi:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/ http://www.oasis-open.org/committees/ebxml-msg/schema/envelope.xsd"><soapenv:Header xsi:schemaLocation="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd"><eb:MessageHeader eb:version="2.0" soapenv:mustUnderstand="1"><eb:From xmlns:axis2ns1561="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd"><eb:PartyId xmlns:axis2ns1562="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd" axis2ns1562:type="DUNS+4">8097318700000</eb:PartyId></eb:From><eb:To xmlns:axis2ns1563="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd"><eb:PartyId xmlns:axis2ns1564="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd" axis2ns1564:type="DUNS">0070367590000</eb:PartyId></eb:To><eb:CPAId xmlns:axis2ns1565="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd">OrderCreate</eb:CPAId><eb:ConversationId xmlns:axis2ns1566="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd">7229ce0c-4b6a-419c-b301-ef28708fda68</eb:ConversationId><eb:Service xmlns:axis2ns1567="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd">uri:OrderCreate</eb:Service><eb:Action xmlns:axis2ns1568="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd">SendResponseEnd</eb:Action><eb:MessageData xmlns:axis2ns1571="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd"><eb:MessageId xmlns:axis2ns1572="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd">1dac9c73-bba3-4fc3-a756-0134872b03d2</eb:MessageId><eb:Timestamp xmlns:axis2ns1573="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd">2008-05-28T10:33:55Z</eb:Timestamp></eb:MessageData><eb:DuplicateElimination xmlns:axis2ns1574="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd" /></eb:MessageHeader><eb:AckRequested eb:signed="false" eb:version="2.0" soapenv:mustUnderstand="1" /></soapenv:Header><soapenv:Body><eb:Manifest eb:id="Manifest" eb:version="2.0"><eb:Reference eb:id="Payload-1" xlink:href="1dac9c73-bba3-4fc3-a756-0134872b03d2-body1" xlink:type="simple" /></eb:Manifest></soapenv:Body></soapenv:Envelope>
On the Ack, B2B is sending the following:
SOAPAction="ebXML"
Content-Type=multipart/related;type="text/xml";boundary="----=_Part_29_18537968.1211985238867";start="<ebxheader-0A27EBC811A2FF31B3B00000C6520000>"
Content-Length=1744
------=_Part_29_18537968.1211985238867
Content-Type: text/xml
Content-ID: <ebxheader-0A27EBC811A2FF31B3B00000C6520000>
<?xml version="1.0" encoding="utf-8" ?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:eb="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd" xsi:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/ http://www.oasis-open.org/committees/ebxml-msg/schema/envelope.xsd http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd"><env:Header><eb:MessageHeader env:mustUnderstand="1" eb:version="2.0"><eb:From><eb:PartyId eb:type="ebMS Identifier">0070367590000</eb:PartyId></eb:From><eb:To><eb:PartyId eb:type="ebMS Identifier">8097318700000</eb:PartyId></eb:To><eb:CPAId>SendResponseEnd</eb:CPAId><eb:ConversationId>7229ce0c-4b6a-419c-b301-ef28708fda68</eb:ConversationId><eb:Service>urn:oasis:names:tc:ebxml-msg:service</eb:Service><eb:Action>Acknowledgment</eb:Action><eb:MessageData><eb:MessageId>Helena Operating Unit@0A27EBC811A2FF31B4400000C6530000</eb:MessageId><eb:Timestamp>2008-05-28T14:33:58.000Z</eb:Timestamp><eb:RefToMessageId>1dac9c73-bba3-4fc3-a756-0134872b03d2</eb:RefToMessageId></eb:MessageData></eb:MessageHeader><eb:Acknowledgment env:actor="urn:oasis:names:tc:ebxml-msg:actor:toPartyMSH" env:mustUnderstand="1" eb:version="2.0"><eb:Timestamp>2008-05-28T14:33:58.000Z</eb:Timestamp><eb:RefToMessageId>1dac9c73-bba3-4fc3-a756-0134872b03d2</eb:RefToMessageId></eb:Acknowledgment></env:Header><env:Body/></env:Envelope>
------=_Part_29_18537968.1211985238867--
They send us Service: uri:orderCreate; Action: SendResponseEnd; CPAID: OrderCreate.
We send in the Ack:
Service: urn:oasis:name:tc:ebxml-msg:sercice; Action:Acknowledgment: CPAID:SendResponseEnd
Where is it pulling the CPAID? or why is it using the Business Action Name?
The message shows complete on our side, but does not get completed on TP side, and since they are they are the initiator they retry 2 times befoer they stop and this is causing duplicte errors on our side. They are using Nexus ebms engine.
Any info on this is appreciated. We are using ebms 2.0
Thanks
PT

SAP System inconsistency for Inbound delivery / MIGO and a "sap note"

Hello Friends ,
After following SAP instruction on how to remove the inconsistency between posting GR through MIGO (Inv. mang.) and the reflection of the goods movement status in the inbound delivery document - done that using sap note 570991
the problem is that the system start behaving in a weird way throwing unjustified Error messages for any suggested goods receipt using MIGO with reference to inbound
for example after creating an inbound delivery document and trying to post it via migo , an error will pop up
- Inbound delivery storage location cannot be changed to here Message no. VLA316
the thing is i didn't even maintain any storage location entry up to that point and yet i cannot post any stock !!
also another error like
- Inbound delivery batch cannot be changed to *** here
which doesn't make any sense because there is not batches in the inbound document !!
i think this behavior is coming from the "Document Flow Update for Stock Postings" inbound indicator at the shipping parameter at client level customization
i need help on how to overcome this annoying SAP Bug/Problem specially i am in a post go live critical situation

Hi,
The messages you mentioned were introduced to avoid inconsistency between inbound delivery and IM, through the note: 1050944 - GR for inbound delivery using inventory mgmt as of ECC 6.00
If the messages are issued incorrectly, then you may check for SAP notes (I couldnt find anything relevant) or raise an OSS ticket to SAP.
Regards,
AKPT

Ack for Inbound messages

Similar Messages

Maybe you are looking for