Can you just try to use something like /B2B/TestNRO instead of the long name you use now?
Re: NRO Not Incrementing
Re: NRO Not Incrementing
Dimitri,
Got it to work!
It was not an issue with the length of the name but it was how I defined my constants. For X12, I wanted to specify a unique Control Number for ST02/SE02. What I did was the following:
I defined the following constant for ST02:
$B2B_UEBNRTestNRO$B2B_END_UEBNR
And the following constant was defined for SE02:
$B2B_UEBNR_BEFORETestNRO$B2B_END_UEBNR
Defining the constants this way updated updated the counter. However, the NRO count in the B2B Integration Cockpit still does not reflect the last count. Bug perhaps???
Thanks again for all your support - really appreciate it!!
Take care,
Dave
Re: NRO Not Incrementing
I stand corrected. The counter is being updated in the NRO Integration Cockpit. I was looking at the log which reflected the changes I manually made to the NRO.
Cheers,
Dave
Re: how to get receiver soap message in sap pi
Hi,
i think your are saying about payload.
But i am asking how to get target message as soap message.
Re: Error in EDI Separator Receiver: EDIFACT message fails: null object loaded from local variable 'cDescr'
For those people that still struggle with this fix: I have heard by SAP that the package you can download in SWDC was not compiled correctly. SAP will provide shortly a correct package. I have got a preliminary archive out of the Incident by the developer and it has fixed the issue.
Re: Error in EDI Separator Receiver: EDIFACT message fails: null object loaded from local variable 'cDescr'
Hi Helmut,
Thank you for your valuable feedback.
Once SAP comes back with the OSS note, referring to the correct SP level, please share it in this thread and close it.
Thank you
Dimitri
Re: how to get receiver soap message in sap pi
Anything specific that you are looking in soap message? Do you have any adapter modules?
May be try xpi inspector
Michal's PI tips: XPI inspector - new functions and features (graphical message flow display)
B2B : ISA,GS and ST Segments Counters in EDI using Number Range Objects
Dear Experts,
We are using one NRO objects to populate numbers for ISA/D_I12 & IEA_D_I12 and through graphical mapping we are assigning the generated number to header and trailer segments shown below.
Same like different NRO Objects for (GS ,GE)and (ST, SE) segments to populate D_28 and D_329 in 810.
When It is single IDOC It fetches the values from the Corresponding NRO objects and passing during run time properly as the number generation happens only once in runtime.
But in case of collective IDOC, then the problem occurs here.I am configuring multipleNumbersPerMessage to generate multiple NRO numbers in a single payload,But the problem is different numbers are generating and is assigning as the $B2B_UEBNR<nroName>$B2B_END_UEBNR is passing to both header and trailer segments because of multipleNumbersPerMessage and thus Header segments does not matches with trailer segment number.
Here the numbers are generating sequentially as many times $B2B_UEBNR<nroName>$B2B_END_UEBNR occursand header and trailermismatches.
How can i assign same number of header segment to trailer segment in this case.?
Or please share any other ideas on control number generation ?Please help.
Regards,
TIBIN JOSEPH
Re: NRO challenges
Dear All,
Please share any possibilities on below thread.
Regards,
Tibin
Re: B2B : ISA,GS and ST Segments Counters in EDI using Number Range Objects
Hi Tibin,
Take a look at NROs for multiple UNH messages within one EDIFACT interchange
Perhaps you can find a lead or an idea.
Kind regards,
Dimitri
Re: B2B : ISA,GS and ST Segments Counters in EDI using Number Range Objects
Dear Dimitri,
Thanks .. ...I applied the same concept of $B2B_UEBNR<NRO Object>$B2B_END_UEBNR &
$B2B_UEBNR_BEFORE<NRO Object>$B2B_END_UEBNR.
But suppose multiple payloads are triggering parallel simultaneously means will it make problem in determining Number's from NRO?.
For Example : Payload 1 and Payload 2.
While assigning Number range using $B2B_UEBNR<NRO Object>$B2B_END_UEBNR in Payload 1for ST header segment counter ,now the$B2B_UEBNR_BEFORE<NRO Object>$B2B_END_UEBNR is used to determine the footer SE segment counter of payload 1.
But when Payload 2 is processed in parallel means new number can generate while processing ST header segment counter for Payload 2 using $B2B_UEBNR<NRO Object>$B2B_END_UEBNR and will is there any chance of applying this number to SE segment counter of Payload 1 using $B2B_UEBNR_BEFORE<NRO Object>$B2B_END_UEBNR .I mean to say if multiple messages are processed parallel in real time will such kind of issue happen?
Regards,
TIBIN JOSEPH
Re: B2B : ISA,GS and ST Segments Counters in EDI using Number Range Objects
I remember a similar problem posted within this community. Please do have a search. I'm sure you will find it.
Re: as2 sender adapter error
Re: SAP PI AS2 Sender Cannot Decrypt Message
Hi Rommel,
Please make sure you are using the same algorithm while encrypting and decrypting, we had a similiar issue where Sender has mentioned 3DES algorithm but the key was created using DES. Once they have changed the encryption to DES it is working fine.
Thanks,
Prudhvi
b2b as2 sender problem
After reading the blogs and helpful threads, I have run AS2 demo successfully with mendelson .
But I still have problem to receice AS2 from WalMart.
find error in b2bic log:
AS2_VERSION: 1.1; MESSAGE_ID: <20141226041451A0B7256E@146907777000001>; AS2_TO: CC_AS2_SENDER_WALMART; AS2_FROM: 146907777000001; FROM: GVBe2Bzy; SUBJECT: EDIINTDATA; CONTENT_TYPE: application/pkcs7-mime; smime-type=enveloped-data; name="smime.p7m"; CONTENT_LENGTH:1351 |
Cannot decrypt message |
Error occured while decrypting the AS2-message: Cannot decrypt message: org.bouncycastle.cms.CMSException: key invalid in message. |
I did some search, somy says it is JCE problem?
but my demo scenario use 1024bits, it works fine.
or algorithm 3DES to DES, PI does not support 3DES? I use DES in my demo too.
Re: SAP PI AS2 Sender Cannot Decrypt Message
Hi Piyush,
Thanks for the help and sorry for marking your answer as correct late. Again, thanks.
Regards,
Rommel
Re: AS2 sender adaptor error
Hi Dimitri,
The outbound is working perfectly. However, the Inbound is still not working!
The Client is able to post message to an FTP server placed in our Network. However they are unable to reach PO.
The BASIS have deployed certificates well, that's why outbound is working.
In Inbound, there should be a user like PIISUSER, where we need to have a Certificate tab. Into that tab, we need to import the certificates. I think then my inbound will work..
I have to change the ume properties but unable to locate where we need to change so that certificates tab appear in the user
Harish
Reuse MDN data Type
HI
I have eight ourbound scenarios and seven inbound scenarios.
I created asynchronous MDN for one outbound scenario, which is from SAP to AS2. The MDN is sent frm AS2 to SAP ECC system
I created DT, MT, SI for both source and response. Then I created MM and OM also for the same. I created an AS2 adapter for sender side. I have used Transport Protocol AS2 MDN and Message protocol AS2 MDN XML. and a reciver SOAP adapter for ECC system.
Can I use the same DT, MT and SI for all outbound scenarios?
Regards
Harish
Re: b2b as2 sender problem
Hi,
We had this issue when we first started testing with longer keys and we followed the steps in this blog to have the system work for unlimited strength keys:
B2B Adapters - Updating to JCE Unlimited Strength Jurisdiction Policy
Regards,
Ryan Crosby
Re: AS2 sender adaptor error
Hi Harish,
If they are unable to reach the PO system then it sounds like it may be a firewall problem. We have our AS2 only reachable via reverse proxy through web dispatcher so that we do not have our PO instance running in the DMZ. Maybe you have something like this setup as well on your network?
Regards,
Ryan Crosby