Regarding error from Trading Partner Management in SAP standard package

[munireddy_pulagam]

callpdscripterror.pngHi,

I Implemented an Iflow to trigger IDOC DESADV.DELVRY03 from SS4 to mendelson test server using Integration advisor, TPM and CI applications. It was running fine and we are able to see the output EDI in mendelson. few days ago i faced an error related to "callPDScript" in runtime(plz see attachment for error message). idocsendererror.png

when i click on that callPDScript.groovy it is throwing an error message as script not found in script collections artifact but i didn't made any changes in that standard package and TPM also.

Please help me to resolve this issue.

[munireddy_pulagam]

Hi,

Can any one share procedure to implement B2B scenarios using Integration Advisor, Trading Partner Management, Cloud integration and Partner Directory, All these applications playing an important role in implementation of B2B scenarios in SAP CPI cloud foundry environment.

Requesting to suggest what are the main parameters needs to be checked while implementing B2B scenarios for outbound and 997.

Related to Integration Advisor there is one video in OpenSAP course and please suggest any blog or information for remaining capabilities configuration details and main focus points

Thank you.

[munireddy_pulagam]

edierror.png

Hi,

this issue not resolved yet and getting the same error for inbound and outbound flows at run time and at the same time we are getting an error status code:02 in SAP System.

Again created a flow from the scratch but still same issue

Please help me to resolve this issue

[Sriprasadsbhat]

Hello Muni,

Pleaes check whether script collection mentioned imported or not.If not goto API businesshub and import the script collection mentioned ( which is available in TPM related content ),

Regards,

Sriprasad Shivaram Bhat

[munireddy_pulagam]

Hi Sriprasad,

it is a standard package (configure only package) i didn't made any changes and Script collections artifact is already available in that package but that run time script(callPDScript) not available in that script collection.Total 15 scripts are there in that collection since we copied it