IDoc Acknowledgement - ALEAUDIT for partner type B

Hi,
I have a scenario where ALEAUD ack required for partner type B instead of LS.
What are the ways by which i can configure ALEAUD ack for partner type B?
Regards,
Anurag

Hi Anurag,
ALE AUDIT is the technique of using IDocs for communication.
ALE Audit it is used to check the cross-system IDoc flow and posting the data in the partner system.
please gone through this related blog blog , it may be helpful for you.
http://wiki.sdn.sap.com/wiki/display/Snippets/ALEAuditfor+DEBMAS
Regards,
Sudeepth

Similar Messages

Idoc to File. Partner type as 'KU' and 'LI'.. Acheivable w/o using Party's?

Hi all,
Idoc to File scenario.
I have the receiver partner type as 'KU' and sender partner type as 'LI'.
I want to create the scenario without using party for these partner Types.
Is it possible for me to create the B2B scenario without using party's?
Is it mandatory that we need to use partys and Identifiers for these kind of scenarios?
Kindly let me know if anyone has idea on this.
Thanks
-Seema

Hi Seema,
I appreciate that you chose to go with the parties
That should be called a good design decision.......
Now answering your query regarding the party identifiers
Idoc to File :
<SNDPOR>SAPDL1</SNDPOR>
<SNDPRT>LI</SNDPRT>
<SNDPRN>90000</SNDPRN>
<RCVPOR>SAPXI</RCVPOR>
<RCVPRT>KU</RCVPRT>
<RCVPFC>SP</RCVPFC>
<RCVPRN>36</RCVPRN>
For Sender Party (say party INTERNAL)
Agency : LD1_001
Scheme: ALE#LI
Name: 90000 (vendor number set in WE20 in the R/3)
For Receiver Party (say party EXTERNAL)
Agency: LDI_001 (SID_<client> BS as defined in SLD)
Scheme: ALE#KU#AG (AG for partner function SP)
Name: 36 (customer number set in WE20 in the R/3
This will resolve the IDoc header data into the following XI SOAP header information:
Sender Party - INTERNAL
Sender Service - LD1_001 (say this is the business system defined for logical system SAPLD1
Receiver Party - EXTERNAL.
Though, you can determine the receiver party alongwith the Receiver Service later at RCV DETERMINATION step, as I have said earlier.
Yes, for outbound you have to maintain the identifiers for Sender Party type LI, but you can still skip the Receiver KU type and update the SOAP header at RCV DET step.
File to Idoc:
<SNDPOR>SAPXI</SNDPOR>
<SNDPRT>KU</SNDPRT>
<SNDPRN>36</SNDPRN>
<SNDPFC>SP</SNDPFC>
<RCVPOR>SAPDL1</RCVPOR>
<RCVPRT>LS</RCVPRT>
<RCVPRN>MAINSAP</RCVPRN>
For Sender Party (say party INTERNAL)
Agency: LD1_001 (SID_<client>)
Scheme: ALE#KU#AG
Name: 36
For Receiver Party (say party EXTERNAL)
Because the RCVPRT value is LS , no need to set the Receiver Party for that.
But if you want to have some Receiver Party value for the same you can use Header Mapping in receiver agreement.
Mandatory Setup in Receiver IDoc Adapter:
Set the indicator - Apply Control Record Values from Payload
Remember to set the Identifiers in the Identifiers Tab in Idoc channel.
Sender:
Agency : LD1_001 Scehma : ALE#KU#AG
Receiver:
Agency: LD1_001 Schema : ALE#LS
I am not sure why this ALE#LS entry is required, but according to my experience if we don't have that entry, the Idoc Adapter throws error while converting the Receiver Party (considering you use party in the ID configuration for both Sender and Receiver).
Yes you are right, you can hard code the SNDPRN, RCVPRN values in the mapping and can take the values from payload...........for that set the following Indicators in Idoc channel:
Take Sender from Payload
Take Receiver from Payload
Let me know if you have any concerns or any additional observation you make while configuring the scenarios. Thanks.
Regards,
Suddha

Idoc Acknowledgement ALEAUD.ALEAUD01

Experts,
I have scenario like this: File(File system) XI/PIIDOC (R/3 sytem), this scenario works fine as is.
Now, i have to send back an IDOC acknowledgement from R/3 system to XI system. I used the link
[https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df56eb]
and all configuration is in place. some times it works, n some time it wont.. this is beacuse I make some permutation n combination of changes, in some of the steps mentioned in the URL.. so, I dont know where I am going wrong..
Note: I did read related SDN posts..
your answers are highly appriciated.
Thanks!

Hi Prema,
1. Was the IDOC was created successfully?
-> Check whether IDOC was created correctly using transaction WE05/WE02/BD87. The issue could be due to partner profile setting, port setting or conditioning setting of your ALE distribution model.
2. Was the IDOC was sent successfully?
-> Check whether number of created IDOC using transaction WE05/WE02/BD87 match with the number of IDOC going thru PI? If it is, then the IDOC was NOT created, and you might want to check the background job that runs RBDSTATE using transaction SM36/SM37
3. Was the IDOC stuck in the PI?
-> You might want to check using SXI_MONITOR and try to fix the issue
Regards,
Lim...

How to find IDOC Function Module for Basic Type:ORDERS05

Hi,
What is the Transaction Code to locate the Function Module linked to the IDOC Basic Type & IDOC Message Type?
Appreciate Your Help.
Thanks,
Kannan.

Hi Seshu,
Thanks for your reply. While creating a Custom IDOC, How do I link the IDOC Function Module and Basic Type. Appreciate Your Help.
Thanks,
Kannan.

IDoc parallel posting for message type of DESADV

The DESADV (Delivery Advice) logic is complex and it takes long time than expected. We want to improve its performance by posting DESADV IDocs in parallel.
Currently, the "Input type" of DESADV's function module is 1, which means parallel run is not enabled. (In tcode BD51). In addition, DESADV is configed as "Immediately" instead of "collected run". We will trigger DESADV every 30 mins, about 500-1000 IDocs will be created automatically and then be posted.
I want to know:
Is it possible to enable DESADV IDocs posting in parallel, how?
Dialog or background is recommended, especially from workload/performance point of view?
Any other concern? such as will data duplicated posting or data lose?
In BD20 (or program RBDAPP01), I noticed there was "Parallel Proc." option which can be selected. Can I just simply change the message type to "collected run" and schedule another background to post those IDocs in parallel?
Any comments is appreciated.
TIA
James

no answer

BD87 idoc inbound error for message type HRMD_A

Hello there,
I am getting below error while fetching Inbound idoc in tcode BD87, see log below from ST22
Short text
    An SQL error occurred when executing Native SQL.
What happened?
    The error "-10328" occurred in the current database connection "LCA".
What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
How to correct the error
    Database error text........: "Mismatch of number of stream members for
     parameter (3) (application 6, database 9)."
    Database error code........: "-10328"
    Triggering SQL statement...: "EXECUTE PROCEDURE "SIM_SIMSESSION_CONTROL""
    Internal call code.........: "[DBDS/NEW DSQL]"
    Please check the entries in the system log (Transaction SM21).
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "DBIF_DSQL2_SQL_ERROR" "CX_SY_NATIVE_SQL_ERROR"
    "/SAPAPO/SAPLOM_CORE" or "/SAPAPO/LOM_COREU07"
    "SIMSCTRL_EXEC_COM"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
   Display the system log by calling transaction SM21.
   Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
   In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
The exception must either be prevented, caught within proedure
"SIMSCTRL_EXEC_COM" "(FORM)", or its possible occurrence must be declared in
the
Do we need SAP_APO in order to install LiveCache?
We have below landsacpe
- SAP ECC 6 EHP4 with SQL server 2005 S BACKEND
-LCAPPS Component release 2005_700 with SP
SAPKIBHD05.
- We dont have SAP_APO component
-SAP LiveCache system have MAXDB 7.7.04.29 as backend.
- Live cache client is installed on same SAP ECC system where we have SAP ECC EHP4 system.
any suggestion how to resolve it?
Mani

>
Mani wrote:
> I installed a standalone server and i need it only for SAP HR (specifically Idoc processing in SAP HR Human capital management module). But i am getting error while running ibound idoc process.
> So Do i still need SAP_APO component?
I never heard of this specific scenario for liveCache usage in the past 7 years working in SAP support on the liveCache component.
Might be useful if you provide some more details (documentation, notes, links) that describe this usage scenario.
In any case you will need to have a liveCache version that is compatible to your application ABAP coding.
The error message you posted indicates that your liveCache version does not fit your application version (or vice versa).
> I installed SAP MAxDB and LiveCache buid using Installation master DVD for SAP ERP. So i think i followed the right method as specified in installation guide.
Be precise, please. Which installation guide? There are hundreds of them - not THE installation guide.
> Secondly can you help me something specific to my problem in coding form?
Already did.
> i tried in LC10, using LCA monitoring i am not able to run SQLDBC trace under
> LCA >> LiveCache Monitoring >> Tools
> but i am not able to execute the same, is it a error or we need to configure something?
Well, the liveCache needs to be integrated into the LC10. You'd do this in transaction SM59 - but as you've followed an installation guide, this would have been covered in it...
> Operational status is active green light, below is file status.
>
>
KNLMSG     KnlMsg     1.098.697     28.01.2011     06:59:55     Database Messages     ASCII
> KNLMSGARC     KnlMsgArchive     8.192     28.01.2011     06:59:50     Database Errors     ASCII
> KNLMSGOLD     KnlMsg.old     342.663     28.01.2011     06:59:50     Database Messages (OLD)     ASCII
> KNLTRC     knltrace     6.209.536     28.01.2011     06:59:56     Database Trace (Raw/Binary)     BINARY
> BACKHIST     dbm.knl     570     10.01.2011     06:18:41     Backup History     ASCII
> DBMPRT     dbm.prt     133.843     29.01.2011     11:41:27     Database Manager Log File     ASCII
> DBMPAHI     L00.pah     214.225     10.01.2011     06:18:16     Database Parameter History     ASCII
> LCINIT     lcinit.log     15.299     28.01.2011     07:00:00     LiveCache Initialisation     ASCII
> LCINITCMD     lcinit.bat     3.047     28.10.2008     14:45:51     LiveCache Initialisation Script     ASCII
> LCINITHIS     lcinit.his     46.742     28.01.2011     07:00:00     LiveCache Initialisation History     ASCII
> INSTPRT     dbm.ins     863.981     10.01.2011     06:18:47     Installation Log File     ASCII
> DIAGDIR     File     0     10.01.2011     06:18:18     Diagnose History     DIRECTORY
> ANALYZER     analyzer     0     29.01.2011     00:00:36     DB Analyzer File     DIRECTORY
> LCTRC#init.his     lcinit.his     46.742     28.01.2011     07:00:00     LiveCache Trace (ASCII)     ASCII
> LCTRC#init.log     lcinit.log     15.299     28.01.2011     07:00:00     LiveCache Trace (ASCII)     ASCII
> LCTRC#_apo_version.txt     lc_apo_version.txt     164     28.01.2011     07:00:00     LiveCache Trace (ASCII)     ASCII
>
> any clue whats wrong?
> Mani
The only thing this tells us is: the liveCache instance itself apparently comes up and writes out the standard log files.
That's it.
As I already tried to explain, the problem seems to be the dependence between your application and the liveCache version.
Usually I'd recommend to open a support message for this, but the colleagues would (hopefully) ask the same questions as I did.
regards,
Lars

Error: 0 communication IDoc(s) generated for message type

what is this??..wher i need to screw this error.

Hi Priyank,
Just cross check with this weblog:
ALE configuration for pushing idocs from SAP to XI
Regards,
Sachin

Wrong Partner Type in IDoc with message type REMADV

Dear all,
We have created 2 IDocs, one for outbound (first in one company code) and one for inbound (receiving company code) with transaction F110 (message type REMADV, Idoc basic type PEXR2001). However, for the first outbound IDoc we have created, we have the wrong Partner type (we would like it to get type KU (customer)) LS (Logic system).
Does anyone know how to change the partner type from the Idoc generationg?
Many thanks,
Ronny

Hi,
Welcome to SDN.
Please delete the exisiting outbound partner profile (WE20) for message type REMADV which under partner type LS (Logical System) and setup new outbound partner profile for partner type KU (Customer).
Regards,
Ferry Lianto

Output type for movement type for IDOC creation

Dear Experts,
Can anybody tell how to create "Output type for different movement types for IDOC creation"
Specially for Movement type used for Inbound & outbound.

Hi,
pls find below link's
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/abap/idoc%2bsteps
BAPI & IDOC material
IDOC Scenario Steps
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://sap.niraj.tripod.com/id51.html
http://www.thespot4sap.com/Articles/SAP_ALE_IDOCS.asp
Changing fields in an Idoc segment
Regards
Raj.

Maitain Partner Type Values for Organisational Unit

Please give me the TCode for Maitaining the Values for Partner Type ORGANISATIONAL UNIT (O).
Regards
Jogeswara Rao

Use tcode PA30
SAP Menu -> Human Resources -> Personnel Management -> HR Master Data -> PA30 - Maintain HR Master Data (Employee Master Data.

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

Idoc acknowledgement message to web service

I am trying to set up the scenario SOAP sender>XI>IDoc Receiver.
I have exposed the outbound, synchronous message interface as a web service, and I'm planning to use sync-async bridge in BPM.
My problem is: I need a response message from SAP. Can I use an iDoc acknowledgement message for this purpose? If this is the case, how do I set up SAP to send this acknowledgement message to XI, and do I have to configure an iDoc sender channel for this purpose?
Any comment is appreciated!
Thanks,
Håvard

One option - not a ABAP expert but this is what I understood with my discussions with my ABAP team when we were coveringt he same issue -
In the Idoc Inbound Processing Code - write a ABAP Exit that after processing the Idoc will trigger the RBDSTATE report to trigger the AleAudit back to XI and XI will send it back to R3.
It is surely possible, as the Aleaudits are triggered by RBDSTATE report instead, you can manually makde the Idoc procesing code to trigger this report immdeitaly and so on.
An Abap , Ale_Idoc specialist will have the answer to this in seconds - on how to do this - but am not one
Regards
Bhavesh

RFFOEDI1 - PEXR2002 Partner type other than B

I would like to utilize partner type LS for the PAYEXT(PEXR2002) IDOC. However, in the config for partner profile in the house bank for EDI, I only see partner profiles for Partner Type B? Anyway to use LS as the partner type? I need LS for the interface mechanism I am utilizing.

Larry,
Thanks I did have the LS partner type configured, the issue I was having that in the house bank set-up under EDI, the only partner profiles that come up are those under partner type B. I think it is that way since it is a bank.
The LS partners are not selectable in the house bank config. I think it is that way and only that way, thoughts?
thanks,
John

Regarding Partner Type LI (Vendor) configuration

Hi All,
My scenario is File > XI> IDOC (INVOIC02 Idoc) Partner Type LI
I had configured WE20 in receiving System for Partner Type LI and given the Process code details.
Now in XI what are the steps that i need to configure( For Partner Type LI Vendor Only)?
DO we need to create Parties for both Sender System and Recieving System?
Please suggest with the various steps to be done for Hanling Partner Type LI in XI .
And i think in receiveing SAP system only WE20 is enough for Partner Type LI ... correct me if i am wrong.
Thanks and Regards,
Sridhar Reddy

Sridhar,
I don't think because of change in partner types whether LI or KU...etc settings at xi will chnage :
It is going to be same :
1. Idoc Import .- through IR
2. RFC destination pointing to R3
3. Port creation - IDX1 using the rfc destination created at step 2.
Apart from this partner profiles needs to created at r/3 end .
Regards

ALE for message type BATMAS

Hello
I am trying to generate IDocs for a copy of the message type BATMAS and have added some custom fields to this new custom message type..
1. I have created BD52 entries for this new custom message . But starngely the IDoc created is for message type BATMAS instead of the new custom message type in WE02. I am executing BD21 for the new custom message type . I have checked BD64 and partner profile settings for the new custom msg type. I have activated change pointers for this new message type in BD50 and BD61.
2. I added a new field MCHA LVORM to the fields in BD52 . But the IDoc is not genearted whenever we change deletion indicator(IDoc).. Its creating the IDocs for changing all the other already existing fields.
I'd appreciate any suggestions/help.
Thanks
V

Hi Ravi;
Just so I understand you, an IDOC was successfully created in ECC and sent to an outbound system. Your outbound system, in this case is PI, which is acting as middleware for your ALE. Now you have an error in PI and you can't get it sent to EREC.
I know people don't like getting questions answered with other questions, but why are you using PI in this scenario? Every ALE scenario I've utilized uses HRMD_ABA directly from ECC to the target system (not with a middleware piece included). In WE20, what would be the harm in changing your receiver port to your actual EREC system? Do you have some kind of business logic being executed in PI converting IDOC field values?
If you think you must use PI, then in sxmb_moni, it would be interesting to know the error message for the IDOC there. However, I think it's entirely likely you don't need to use PI at all and could just use a direct RFC between ECC and EREC.
Good luck,
Chris

IDoc Acknowledgement - ALEAUDIT for partner type B

Similar Messages

Maybe you are looking for