Idoc Acknowledgements in SAP PI7.31 Single stack

Hello All,
We are migrating from SAP PI 7.0 to SAP PI7.31 single stack.
in Existing landscape(SAP PI7.0) - sender system ECC is receiving the acknowledgements(ALEAUD) for the idocs sent to PI system where in the port is different i.e. port is receiving back with different Partner Number.
But in SAP PI7.31 single stack, ECC is recieving the acknowledgmenets(ALEAUD) as same as the sender partner number of the idoc sent to PI 7.31 system.
can someone please explain me if it is possible to implement the same functionality as per SAP PI7.0 in SAP PI7.31 single stack as well or is this the Limitation of the product.
Thanks
VR

Hello Experts,
Can someone please suggest me if SAP PI7.31 Single stack can send ALEAUD with different partner number to ECC.
Thank you
VR

Similar Messages

How to track the Inbound child IDOcs in PI 7.4 Single stack

Hi Friends,
I would like to know the procedure of tracking the Inbound child IDocs in PI 7.4 Single stack.
Here is the detailed description.
Say we are getting the data from third party system and the message may have multiple IDOcs in it. The message has processed successfully from PI and reached to the target system(ERP). So, now my question is how to track the IDOc count with in that message.
Please suggest on the same.
Thanks in Advance,
Venkateswarlu.

Hi Hareesh,
Thanks for your inputs. According to the link IDOC Status, Tracking in SAP PI/PO Single Stack I am thinking the required funcionality is not there in PO 7.4, but still i would like to have little more clarity before moving further.
I will explain what what was happening in PI 7.11 so that you can understand what i am looking for in PO 7.4.
We will get the data from third party system in xml format, we had to search for the messages based on interface name and time range within SXMB_MONI. After getting the result(say the output is 100 messages), we will download the values of "Outbound Reference" field(which is a key to find the child messages for messages resulting in an Interface Collection). Below is the snap of Outbound Reference field for your reference.
Now we will go to the table IDXRCVPOR in SE16(within PI) and put the values of Outbound Reference field in Text 24 and execute. Here we will get all the child messages.
Now please let me know if this kind of scenario is possible in PO 7.4.
Thanks,
Venkat.

Suppress Idoc acknowledgement in SAP PI 7.3

Hi Experts,
I need to suppress ALEAUD Idoc acknowledgements in PI. My scenaros is Idoc (ORDRSP) to file pass through.
Aleady entries are maintained for ORDRSP idoc in IDXNOALE table.
in SE16, IDXNOALE--> Selected ORDRSP entry--> change mode --> I have deleted values for NEG and TYPE, when i trigger Idoc from ECC, first time i am not getting acknowledgements but once i trigger automatically NEG value is updating as "X", from next time i am getting acknowledgements.
I have executed IDX_NOALE report in SE38, If i select ORDRSP message type and click on DoNotRequestAcknowledgments, its asking do you want to overwrite for all? if i select yes, all entries are deleted.
Help me to suppress these ALEAUD acknowledgements in SAP PI 7.3.
Attached is the enries i have updated.
Thanks & Regards,
Mohan.

Hi Harish,
I have checked this thread, As i mentioned earlier
I have executed IDX_NOALE report in SE38, If i select ORDRSP message type and click on DoNotRequestAcknowledgments, its asking do you want to overwrite for all? if i select yes, all entries are deleted.
To suppress idoc acknowledgements, do we need to add entries in IDXNOALE table or do we need to delete existing entreis by using report IDX_NOALE?
If i change NEG and TYPE values as empty, first time its working however next time automatically NEG value is updating as "X" due to that i am getting acknowlegement agan in the second time.
I am confused.
Thanks & Regards,
Mohan.

Single stack vs. Dual Stack - Why does SAP recommend single stack?

Hello SAP,
I am a business partner who specializes in infrastructure consulting for SAP solutions. The SAP Consultants I am working with recently have been recommending that customers install single stack systems. I would like to know why? Are there problems with dual stack systems? Is SAP changing things in a later release and they want customers to be prepared for the change?
From an infrastucture point of view this recommendation combined with SAP NetWeaver architecture will result in an explosion of SID names which leads to an explosion of application server instances and DBMS instances and an explosion of installed servers. I know it is possible to combine SIDs into a single DBMS using MCOD and to have multiple application servers in a single physical server, but there are issues with mulitple application server instances and MCOD use which make normal maintenance operations difficult.
I think it would be much better for customers to install dual stack systems and simply adjust the SAP profile parameters to disable one stack or the other. This way, you could still have 1 stack per application server instance and you would not be have to be creative with SAP SID names!!! Creating a DBMS instance or installing an additional server is not a simple nor economical proposition.
Regards,
Zaz

I am a business partner who specializes in infrastructure consulting for SAP solutions. The SAP Consultants I am working with recently have been recommending that customers install single stack systems. I would like to know why? Are there problems with dual stack systems?
The problems are:
- difficult to size and maintain - Java + ABAP will fight for resources (memory,CPU) and there´s not much one can do to tune if either ABAP or Java as dual stack instance on a single box is running nuts (for whatever reason).
- System copies via R3load - if you want to copy a huge system (let´s say ERP 6.0 + Java stack) you need to use sapinst + R3load to do the copy. Imagine if the system is 1 TB or bigger, this is very time consuming
- Upgrades are complicated - if you upgrade a dual stack system you need to run two PREPARES and two upgrades at the same time - there are sync points each upgrade wait for the other to finish --> difficult to plan in sense of runtimes and even more notes/preparation to do (a dual stack SolMan upgrade from 3.2 to 4.0 had almost 100 notes (technical!) and two upgrade preparation guides...)
- interdependencies - example: you run ERP + EP + BI-Java on one system. You upgrade your BI (which is on a different box) to a new support package. Since the BI-Java need to be in sync with the BI ABAP support package you need to upgrade the EP too - and since there´s a direct dependency (doublestack system) you will need to install support packages on your ERP. So you finally end up in having dependency chains that a total different system (BI) will force you to upgrade/patch your ERP. And if you have e. g. a CRM connected to the same EP you will need to patch that too...
Is SAP changing things in a later release and they want customers to be prepared for the change?
No - the possibility of having a dual stack installation will be still there.
From an infrastucture point of view this recommendation combined with SAP NetWeaver architecture will result in an explosion of SID names which leads to an explosion of application server instances and DBMS instances and an explosion of installed servers. I know it is possible to combine SIDs into a single DBMS using MCOD and to have multiple application servers in a single physical server, but there are issues with mulitple application server instances and MCOD use which make normal maintenance operations difficult.
I agree - MCOD is not a good solution for this problem.
I think it would be much better for customers to install dual stack systems and simply adjust the SAP profile parameters to disable one stack or the other. This way, you could still have 1 stack per application server instance and you would not be have to be creative with SAP SID names!!! Creating a DBMS instance or installing an additional server is not a simple nor economical proposition.
There are 36 * 36 * 36 (minus a few reserved) names for SIDs- this should be enough - also for the biggest customers
Of course one could install both and disable the one you don´t need - but this won´t help in dependency thing. If you e. g. install a dual stack instance for CRM and disable the Java part, you can nicely run it. In case of an upgrade, you will need to upgrade the Java part too (see above) although you don´t use it. The upgrade will detect the doublestack and wait for the java instance to be upgraded too. Same is true vice versa. And believe me: you don´t want that
In fact it is better to separate - that´s at least our experience. The main no-go for such a configuration on our side was the dependency thing. Since they are there and you can´t do much about them we decided to have a 1:1 relationship for ABAP backend and Java "frontend". You will get more instances (and names and databases) but you can patch applications independently from each other. So an implementation of a BI patch won´t imply that you finally also patch your ERP production and other systems that connect to that portal.
There are virtualization techniques available to not need more boxes, you can consolidate them on one machine as if you were installing a dual stack so that is not really an issue. This depends, of course, on the platform and database you use (e. g. Oracle does not support production installations in VMWare). We use for our Java instances Solaris on Opteron (or Intel 64bit) and zones/containers and for the ABAP part we use Linux + Xen. Both virtualization methods come with the OS (so no additional $$$) and both are supported by SAP.
The propagated advantage of having a dual stack installation (shared memory access etc.) is so small that it doesn´t outban the additional complexity - which is definitely there.
I hope those arguments will help to understand SAPs (and the consultants) position - get back if you want more
Markus

IDoc Acknowledgement from SAP PI to SAP R/3 Server

Hi Experts,
I am sending an IDOC from sap r/3 to SAP PI. After receiving the IDoc I need to send back one acknowledgement to the sap r/3 server, without reaching the target side. Could you guys please help me?
Thanks
Dipankar

it can send back an acknowledgement IDoc (ALEAUDIT) back to R/3 system
This configuration works for sending ACK message back to the Source system from the Target System and should not be mistaken to enable PI to generate the ACK and send back to the Source system.
What can be done is include the source system as receiver in the receiver determination (SAP system is both at the source and target....alongwith the existing FILE target service)......configure different ID objects for this Source > PI> Source ACK flow .... map required data in the mapping.....depending on your need you can use the target structure IDOC/ PROXY/ RFC.
Regards,
Abhishek.

IDOC Status, Tracking in SAP PI/PO Single Stack

Hi All,
My PO version: 7.4, SP4. I am not sure my questions below are still a limitation in current PI/PO single stack systems, and hence requesting your help for the same.
1) Is there a way we can track outbound idocs in SAP PI/PO single stack similar to PI abap stack IDX5? ( Note:- I couldn't find any option in IDOC monitoring in single stack SAP PO 7.4, SP4)
2) IDOC status is always 0 in SAP PO 7.4 single stack IDOC monitoring. I am not sure if this status is just specific to my PO system. Any setting needs to be applied?
ps: Please post only relevant answers/solutions
Thanks,
Praveen Gujjeti
Message was edited by: Praveen Gujjeti

Hi All,
As per SAP help: Comparison of IDoc Adapter (IE) and IDoc Adapter (AAE) - SAP NetWeaver PI Reference Documentation - SAP Library idoc status and tracking not supported in current PO versions. May be SAP will add this feature in upcoming PO versions
Auditing, Monitoring ,and Tracing Functions
Attribute/Feature
IDoc Adapter (IE)
IDoc Adapter (AAE)
ALE Audit
Supported
Supported
IDoc tracing
Supported (transaction IDX5)
Not supported
IDoc monitoring
Transaction IDX5
Integration with channel monitor and message monitor (as part of Advanced Adapter Engine monitor)
Status tracking -SYSTAT
(analysis and further processing of messages that have not been processed)
Not supported
Not supported
RFC monitoring
Supported
Not supported
Message persistence in the IDoc adapter
Supported
Message correlation information can be stored in IDoc adapter.
Not supported.
Message is persisted in messaging system with correlation data persisted in adapter.
Regards,
Praveen Gujjeti

Unable to see Payload in SAP PI7.31 Single stack

Hello Experts,
We have a scenario of Mail as sender and ECC as reciever using Proxy. We are using SAP PI7.31 single stack.
Here we are reading the file from mail attachment which is in CSV format and sending the data to ECC successfully.
But while to check the payload in Message Monitor, while click on the "Mailattachement-1.csv" it is opening with "No Message Selected".
Can someone please let me know how can I check the payload of the attachement.
Thanks
VR

Hi VR
Check this parameter:
NWA -> Configuration -> Infrastructure -> Java System Properties -> Services -> XPI Service: Messaging System, set property messaging.SyncMessageRemover.removeBody = false
Check also the general parameters for tracing and logging
Saving Message Versions in the AAE (Local Message Processing) - Advanced Adapter Engine - SAP Library
Regards
Javi

SAP PI7.31 Java Single Stack - Default Delete Job Retention period

Hi
anybody know where the Default Delete Job Retention periods can be set ? I'm on a SAP PI7.31 Java Single Stack.

thanks - in milliseconds - very precise.
1) NWA-->Configuration-->Infrastructure -->Java System Properties
2) Go to Services tab, and type XPI and select – XPI Adapter: XI
3) Type “persist” in Properties filter
4) for example Set Retention period in Milli seconds and save
2592000000 = 30 Days

IDOC settings from sap r/3 to sap pi7.3

Hi Guru,
actual problem when i am triggering the idoc from ERP,it is trigeering to the abap stack in sap pi.but i am using idoc_aae adapter at sender side,the message is flowing from sap ERP to file but the message is seen in sxmb_moni,but actually it is not seen in moni .
Please if any one have the idoc setting from sap erp to sap pi7.3. and iam using ICO configuration.
Please help me
Regards
Reddy

Hi,
Please go through the below link :
http://wiki.sdn.sap.com/wiki/display/XI/ALE-Idocconfiguration-+%28R3XIFile%29
Also in your software component version please check whether import of IDocs and RFCs are allowed
from your respective ECC system, and check the ECC system parameters are correctlt maintained or not.
Try out once.

PI 7.4(Single stack) Idoc to file + additional done file

Hi All,
here the requirement : I want to convert Idoc to file in PI 7.4 (single stack) and send to FTP location with time stamp (eg: xxx_06082014123055.txt) and also need to create another empty file with same time stamp (eg: done_06082014123055.txt) after transferring xxx file. when the target system find the done file then it process the xxx file and deletes done file.
one way is I could create a 2 operation mapping and 2 service interface which will then configured in ID as two receiver interface mentioning 'maintain order at Runtime' pointing to same communication channel but the filename had to be created in UDF in mapping.
My question is , Is there any other alternative or better way to achieve this??
ur ideas pls....
Sha

Hi Sha,
You can use the multimapping concept, you will generate two messages and two files, with the second message only with its root element in order to create an empty file. Check these links to know more about the multimapping concept:
Multi-Mapping without BPM - Yes, its possible!
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/90dcc6f4-0829-2d10-b0b2-c892473f1571?overridelayout=t…
Regards.

Want to learn SAP PI 7.4 Single stack

Hi Experts,
I am a beginner in SAP PI and started by journey with SAP PI 7.0. Now, we are upgrading it to SAP PI 7.4 single stack.
I want to learn it as much as possible before the migration but when I search for the topics in SCN, I am getting confused with the different topics and its naming conventions explained. (For Eg PI and PO). So, will it possible for you experts to provide me the links which can actually help me to get the full depth knowledge on PI 7.4 (Single stack). Am just hoping to be a productive member of this SAP family:)
Regards,
Adarsh

Hi Adarsh,
SAP Process Orchestration is the new name of SAP Process Integration (SAP PI). SAP changed the name with the release 7.3 to include the additional features of SAP NetWeaver Business Process Management (nBPM), Advanced Adapter Engine Extended (AEX) and SAP NetWeaver Business Rules Management (BRM).
Source - Latest version is SAP PO 7.4 or SAP PI 7.4 (commonly known as of now). Good part is that PO 7.4 license includes BPM and BRM. Till PO 7.4 SAP still provides the dual stack (ABAP + JAVA) option to install. But going forward it would be single stack (JAVA) only i.e. only swing tool for ESR and ID or NWDS. no more transactions/tocde.
From a developer standpoint:
You got all adapter based on JAVA. IDOC and HTTP are now IDOC_AAE and HTTP_AAE, also proxy scenario can be done using SOAP adapter XI protocol and there is no ccBPM.
Regards,
Sachin Dhingra

SAP PI 7.3 Single stack- Set tracing and logging

Hi experts
We have configured a SOAP to SOAP sync scenario in SAP PI 7.3 single stack(Java Only).
I have sent some test messages from WSNavigator to PI .
But when i checked messages in adapter engine, it is showing*"Unable to retrieve payload or you don't have sufficient authorization to view the content" I am able to monitor payloads of Async messages.
How can we set Logging and trace levels in Single stack PI? I couldn't find any options in RWB os NWA.
Thanks,
Dhanish

Hello Dhanish,
As it was stated by Kenneth in his post, if you would like to see payload of a synchronous message in Message Display Tool (e.g. from Runtime WorkBench), you should set value of property messaging.SyncMessageRemover.removeBody of J2EE service XPI Service: Messaging System to 'false'. Please note that this affects only synchronous messages in final states (DLVD and FAIL).
Regarding the second part of your question - logging. In PI 7.3, you can persist the message in Adapter Framework in two ways - stage it or log it. Staging allows you to edit/restart the message later from the stage where the message was persisted and is relevant for asynchronous messages; logging allows you to only display the logged message and is relevant for both synchronous and asynchronous messages. Please also note that staging affects performance of message processing more greatly than logging, extensive staging (e.g. staging on several processing stages) can even be a reason of performance degradation for processed messages, so if you only need to display details of the message on different processing steps in Adapter Framework, logging should be sufficient. Both staging and logging can be configured using properties xiadapter.stage.conf (for staging) and xiadapter.logger.conf (for logging) of J2EE service XPI Adapter: XI.
Regards,
Vadim

IDoc Acknowledgement Issue in SAP PI 7.3

We have configured IDoc to IDoc scenario between two ECC system using IDOC_AAE adapter. When we run the RBDSTATE program to trigger ALEAUD IDoc it is getting failed in SM58 in ECC system. But when we configure a separate scenario to transfer ALEAUD IDoc from one ECC to other ECC system usin IDOC_AAE adapter then the ALEAUD IDoc reached in target ECC system. In this case there is no error in SM58 of ECC system.
SM58 Error: Commit fault: ASJ.ejb.005043 (Failed in component: sap.com/com.sap.aii.ad
Regards,
Anurag

Hi Anurag, Hasan,
Check the following OSS Notes, they are both addressed to the error you mentioned (appearing under different circumstances, so you might have to choose the right one):
1719180 Handling of multiple acknowledgements in one ALEAUD IDoc
1729575 Sending IDoc acknowledgements fails because of long text
Regards,
Greg

PI 7.31 (single stack) posting to RFC configuration gives this error: om.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: String index out of range: 0 (raised by system extern ...

Getting cryptic error while trying to post to a custom RFC from PI 7.31 single stack.
com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: String index out of range: 0 (raised by system <extern>|pidevhost)
Does anyone recognize this error and/or know of detailed instructions for registering custom RFCs in PI 7.31. I could possibly have configured the target wrong but no error says so.
This is a File-->PI-->RFC scenario. The file processing is super simple and a configuration I have used successfully before. I would assume I'd get a different error if it couldn't parse the file.
Jody

Not shure if you already did but try getting some details with XPI Inspector. Also increasing log level for this category might help. You also may wanna check authorization (even if this should show with a different error text) in ECC using ST01.
My guts feeling is that there is something wrong with payload / signature of RFC.
Cheers
Jens

Archiving and Deleting of XML Messages in SAP NetWeaver PI 7.31 single stack

Hello my XI friends!
Need step by Step Guide to Archiving
and Deleting of XML Messages in
SAP NetWeaver PI 7.31 single stack
Similar to these instructions
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e0afdd69-a8a7-2d10-7e9a-cbf6fa21c5a7?quicklink=index&overridelayout=true
Regards,
Rinaz

Please check the below blog for archiving java only-(XMLDAS)
http://scn.sap.com/community/pi-and-soa-middleware/blog/2011/11/16/aae-archiving-in-sap-pi-711-with-xmldas
For deletion there is standard delete job..
https://help.sap.com/saphelp_nw73ehp1/helpdata/en/48/b2e0036b156ff4e10000000a42189b/frameset.htm
Message was edited by: Hareesh Gampa

Idoc Acknowledgements in SAP PI7.31 Single stack

Similar Messages

Maybe you are looking for