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

Similar Messages

Inbound problem for message type WPUUMS

Dear all,
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

You have to analyze where exactly the problem is.
There are several reasons why the Idoc did not post:
1) The Data you are sending to post document may be wrong. You may have to validate against valid data in Database.
2) Thre may be some mandatory data which you are not passing through IDoc (Idoc data may be missing).
It is not possible to answer a generic question like this with perfect answer.
Best way is to debug and find out why exactly the problem is, if you know the error message (you may see it in Status record of this IDoc).

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

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

IDoc generation with Message Type HRMD_A with filter on Personnel Area

Hello All,
We are facing an issue in generating IDoc using the standard message type HRMD_A.
When we have no filters on the Distribution Model, the IDoc is generated through RBDMIDOC. When we use the filter on BUKRS, it generates the IDoc but gives an error status "Cross-system company code XXXX does not exist". I know to how resolve this issue. But, we tried to filter the changes with Personnel Area this time. So I have used the field PERS_AREA in BD59 with segment type E1PLOGI. When I run the standard report RBDMIDOC it gives the message "No data selected for distribution".
I have checked the field name PERS_AREA from table TBD10, and it is mapped to T500P-PERSA. Change pointers are triggered and stored in BDCP2. Request experts to suggest what could be wrong with this.
Thanks,
Anil

Hello Michele,
If you have added BUKRS in BD59 for the message type, you will see Company Code (not filter1) in your filter criterion in BD64.
Have you included the following code in FILTER_VALUES_SET method of the BADI implementation.
CHECK OTYPE = 'P '.
SELECT * FROM PA0001
           INTO PA0001 WHERE PERNR = OBJID
                       AND   BEGDA <= SY-DATUM
                       AND   ENDDA >= SY-DATUM.
record is valid today, no authorization check
    EXIT.
ENDSELECT.
IF SY-SUBRC = 0.
    FILTER1 = PA0001-BUKRS.   ELSE.
    CLEAR FILTER1.
ENDIF.
Lastly, just make sure the record you are testing for has your desired company code PGPB.
Regards,
Anil

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

Trigger inbound BAPI IDOC for message type ACC_GL_POSTING

I configured our SAP system for inbound GL postings -- message Type ACC_GL_POSTING process code BAPI. I successfully tested all the configuration pieces using WE19.
So how do I trigger the inbound process from my external non-SAP system. I would prefer not create a flat file that is passed by calling EDI_DATA_INCOMING. I also do not want to use BAPI_ACC_GL_POSTING_POST. So what RFC enable FM can I call to pass data and trigger the IDOC generation and processing? Is there anything standard?

I will use the standard RFC enabled function module IDOC_INBOUND_SYNCHRONOUS. No custom abap development will be needed.
Message was edited by:
David F

ERROR: "The IDoc interface is not complete for message type DELINF"

Dear All,
The ERROR happens when I use IDoc inbound test tool:
- Basic type used: DELVRY06
- Basicallly this IDoc is supposed to create inbound PGI of a DO. I just put the DO number in WE19.
But ended up with the error mentioned. Let me know if oyu need more details.
Thanks and regards,
Will.

Hi,
Please check whether the partner profile configuration is done completely such as any message control parameters are fine or not.
Regards
Archanaa

Error In MIGO "Could not determine recipients for message type ACPJMM"

Dear all,
At the time of transaction Goods Receipt(MIGO), I am getting the error message "Could not determine recipients for message type ACPJMM".
System Diagnosis is as below
An IDoc of message type ACPJMM was passed to the ALE layer, but the three receiver fields in the header record were not filled. In this case the ALE layer tries to determine the receivers from the entries in the distribution model. There are no entries available in the distribution model for the above message type
I have check the ALE Settings in we20 and we21
and have assigned the following message types under Logical syste Partner Type
Outbound
ACPJMM
MATMAS
MBGMCR
RSINFO
RSSEND
WHSORD
Inbound
ACPJMM
DEBMAS
FTDABA
FTDACO
FTDACU
INSPECTIONPLAN_CREATE
MATMAS
MBGMCR
RSRQST
WHSCON
I have also created and Assigned a Logical System to the client and have also created a RFC with the same name
I have checked all settings is SALE and they are Fine.
This is a single system
Please help this is really ugrent
Regards
Suhail John

Hi,
Goto table TRWCA (T Code SE30) and deselect all the checked entries.
This should solve your problem.
Regards,
Priyadarshi

Error in ALE service 29 Could not determine recipients for message type MAT

Hi Experts,
While transferring the material using ALE am getting error 29 ie 'Error in ALE service' and message is 'Could not determine recipients for message type MATFET'.
Also i ve recieved the materials with the proper status al the end am getting the above error.
Kindly help me out.
Thanks in advance.

Hi ,
Status 29 means " partner profile not found " . Please check if the recieving partner is configured properly in WE20 in sender system.
Also make sure that the Port and RFC definations are also completed. If the IDoc is manually triggered then please make sure that control record parameters of the idoc are properly filled - if we miss the details ( like wrong port given , wrong basic type for message type - or extended message type ) then also the idoc will fail in status 29 even though the partner profile is properly configured .
Since your idoc is getting generated i think no issues with BD64 since already interested recipeints were populated in control record of idoc.
Regards
Vikas Chaudhary

Problems with PROOF field in idoc (message type HRMD_A)

Hello,
I'm using the standard message type HRMD_A with IDOC base type HRMD_A06 and the function module IDOC_INPUT_HRMD.
I have a doubt with field 'PROOF' when I fill the IDOC. Does anybody know for what is it used? For example, what's going to happen if I put PROOF = 'X' in an update operation?
In my case I have tested that when PROOF = 'X', I receive the following warning in intotype 0001:
    The EMPLOYEE_ORG_ASSIGNMENT-ADMINISTRATOR_GROUP field is not maintainable in dialog, so it is ignored
    The EMPLOYEE_ORG_ASSIGNMENT-ORG_UNIT field is not maintainable in dialog, so it is ignored
    The EMPLOYEE_ORG_ASSIGNMENT-COSTCENTER field is not maintainable in dialog, so it is ignored
but I cannot be sure if these warnings are due to PROFF.
In the change data record screen, I have filled the following fields: plan version ('01'), object type ('P'), object id (employee number), PROOF ('X'), Operation ('U'). Structure for the idoc is EDIDC->E1PLOGI->E1PITYP.
Any help on this?

Hello,
I'm using the standard message type HRMD_A with IDOC base type HRMD_A06 and the function module IDOC_INPUT_HRMD.
I have a doubt with field 'PROOF' when I fill the IDOC. Does anybody know for what is it used? For example, what's going to happen if I put PROOF = 'X' in an update operation?
In my case I have tested that when PROOF = 'X', I receive the following warning in intotype 0001:
    The EMPLOYEE_ORG_ASSIGNMENT-ADMINISTRATOR_GROUP field is not maintainable in dialog, so it is ignored
    The EMPLOYEE_ORG_ASSIGNMENT-ORG_UNIT field is not maintainable in dialog, so it is ignored
    The EMPLOYEE_ORG_ASSIGNMENT-COSTCENTER field is not maintainable in dialog, so it is ignored
but I cannot be sure if these warnings are due to PROFF.
In the change data record screen, I have filled the following fields: plan version ('01'), object type ('P'), object id (employee number), PROOF ('X'), Operation ('U'). Structure for the idoc is EDIDC->E1PLOGI->E1PITYP.
Any help on this?

Error MSG : Create a partner profile for message type 'MATMAS'

Getting Error MSG : Create a partner profile for message type 'MATMAS'
While running LSMW Idoc generation process

See the below link and it has all screen shots how to configure ALE like partner profile,logical systems,RFC
http://searchsap.techtarget.com/general/0,295582,sid21_gci1130337,00.html

LSMW: ALE/IDOC, getting the Create a partner profile for message type

Hi Gurus,
In my current project, i need to upload the employee data using the ALE/IDOC method with the LSMW
when i'm generating the idoc in the 13th step, its posing the information message stating that:
Create a partner profile for message type 'ZEMP_MSG'
In partner profile i already assigned the message type .
How to solve this issue, <inappropriate urgency removed by moderator>
Thnks&regards,
sree
Edited by: Thomas Zloch on May 13, 2011 9:55 AM

This forum's aim is not only to search for information and ask the members questions, but also to share knowledge. When you have asked a question and found a solution, do share with the rest.

ALE settings error "Too many recipients found for message type" urgent

Hi all ,
please help me to solve this issue !!!!!!!!
i done with ale settings .
in the bd64 , orders message type is used in 2 different model view for 2 different systems
when i create po it is giving error in output "Too many recipients found for message type ORDERS in the ALE model"
how can i rectify this error.
Thanks

Hi,
Try to redefine your distribution model to have both receivers of your message type ORDERS in one "model view".
Regards,
Jakub

Error - Could not determine recipients for message type ACP JMM

Hi Guru's
I am facing a problem while doing goods receipt(migo), "Could not determine recipients for message type ACPJMM".
Right answer will be rewarded
Regards

hi
If you want to deactivate this goto SM30, enter the table TRWCA, deactivate the component
RWEX - Idoc Output, External Accounting.
this should solve your problem.
refer following links
Message type ACPJMM
Message no. B1003""Could not determine recipients for message type ACPJMM""
MIGO and MIRO Problum
regards
kunal
Edited by: kunal ingale on Sep 2, 2008 11:46 AM

BD87 idoc inbound error for message type HRMD_A

Similar Messages

Maybe you are looking for